Triple
T9081715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pur River |
E217642
|
entity |
| Predicate | isNavigableSection |
P12104
|
FINISHED |
| Object | lower reaches |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: lower reaches | Statement: [Pur River, isNavigableSection, lower reaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigableSection Context triple: [Pur River, isNavigableSection, lower reaches]
-
A.
navigableInSection
chosen
Indicates that something can be successfully moved through, accessed, or traversed within a specified section or segment.
-
B.
hasNavigationSection
Indicates that an entity includes or is associated with a specific navigation section used for guiding or organizing access to its parts or related content.
-
C.
navigableFor
Indicates that one entity (such as a path, route, or medium) can be traversed or used for movement by another entity (such as a vehicle, vessel, or agent).
-
D.
isNavigableNear
Indicates that an entity can be traversed or passed through in close proximity to another specified entity or location.
-
E.
isNamedSectionOf
Indicates that one entity is a specifically named section or subdivision that forms part of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9608a82481908918821884ba5796 |
completed | April 1, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.