Triple
T6323646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conchos River |
E141805
|
entity |
| Predicate | majorRiverIn |
P57854
|
FINISHED |
| Object | northern Mexico |
—
|
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: northern Mexico | Statement: [Conchos River, majorRiverIn, northern Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRiverIn Context triple: [Conchos River, majorRiverIn, northern Mexico]
-
A.
largestInflowRiver
Indicates that one river has the greatest volume of water flowing into a specified body (such as a lake, sea, or another river) compared to all other contributing rivers.
-
B.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
C.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
D.
isMajorWatercourseOf
chosen
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
E.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e38f1c81909c7e90b520602bae |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.