Triple
T36073654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nu Jiang |
E1043433
|
entity |
| Predicate | hasDownstreamName |
P188144
|
FINISHED |
| Object | Thanlwin River |
—
|
NE NERFINISHED |
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: Thanlwin River | Statement: [Nu Jiang, hasDownstreamName, Thanlwin River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDownstreamName Context triple: [Nu Jiang, hasDownstreamName, Thanlwin River]
-
A.
hasDownstreamConfluence
Indicates that one watercourse or flow feature joins or merges into another at a point located further downstream.
-
B.
hasDownstreamArea
Indicates that one entity is associated with an area located downstream from it, typically receiving flow, influence, or impact from the upstream entity.
-
C.
downstreamFrom
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
-
D.
hasDownstreamDam
Indicates that one water barrier or dam is located downstream from another along the same watercourse.
-
E.
hasLowerCourseName
Indicates that one course’s name is lexicographically or alphabetically lower (comes before) another course’s name.
- F. None of above. chosen
Provenance (4 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:08 p.m.