Triple
T32785082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Chama Wilderness |
E838471
|
entity |
| Predicate | riverSegment |
P120790
|
FINISHED |
| Object | middle Rio Chama |
—
|
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: middle Rio Chama | Statement: [Rio Chama Wilderness, riverSegment, middle Rio Chama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverSegment Context triple: [Rio Chama Wilderness, riverSegment, middle Rio Chama]
-
A.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
B.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
C.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
D.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
E.
watercourseSectionOf
chosen
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:14 a.m.