Triple
T26587026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barail Range |
E667236
|
entity |
| Predicate | hasRiverOrigin |
P140514
|
FINISHED |
| Object | tributaries of the Barak River |
—
|
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: tributaries of the Barak River | Statement: [Barail Range, hasRiverOrigin, tributaries of the Barak River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverOrigin Context triple: [Barail Range, hasRiverOrigin, tributaries of the Barak River]
-
A.
hasHeadwatersOf
chosen
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
-
B.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
-
C.
hasHydronymOrigin
Indicates that something derives its name from a body of water or hydrological feature.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 2:06 a.m.