Triple
T1689054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuma, Arizona |
E36508
|
entity |
| Predicate | riverCrossingImportance |
P1970
|
FINISHED |
| Object | historic Colorado River crossing point |
—
|
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: historic Colorado River crossing point | Statement: [Yuma, Arizona, riverCrossingImportance, historic Colorado River crossing point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossingImportance Context triple: [Yuma, Arizona, riverCrossingImportance, historic Colorado River crossing point]
-
A.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
B.
notableRiverCrossingRole
chosen
Indicates that an entity plays a significant role as a location or feature involved in the crossing of a river.
-
C.
majorPortOnRiver
Indicates that a port is a primary or significant harbor facility located on the banks of a specified river.
-
D.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
E.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.