Triple
T29536510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado River at Parker |
E749360
|
entity |
| Predicate | isCrossingPointBetween |
P50696
|
FINISHED |
| Object | Arizona |
—
|
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: Arizona | Statement: [Colorado River at Parker, isCrossingPointBetween, Arizona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCrossingPointBetween Context triple: [Colorado River at Parker, isCrossingPointBetween, Arizona]
-
A.
hasCrossingPoint
chosen
Indicates that two or more entities intersect or share at least one common point in space or along their paths.
-
B.
isCrossBetween
Indicates that one entity is a hybrid or intermediate form resulting from the combination or mixing of two other entities.
-
C.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
D.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
E.
isOnlyDirectCrossingBetween
Indicates that one entity serves as the sole direct crossing (e.g., bridge, passage, or connection) between two other entities, with no alternative direct crossing available.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cc62a0c8190af1c447b702bd368 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:58 p.m.