Triple
T35184281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Grande Pyramid |
E1015941
|
entity |
| Predicate | summitCoordinateLongitude |
P68328
|
FINISHED |
| Object | -107.4267 W |
—
|
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: -107.4267 W | Statement: [Rio Grande Pyramid, summitCoordinateLongitude, -107.4267 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitCoordinateLongitude Context triple: [Rio Grande Pyramid, summitCoordinateLongitude, -107.4267 W]
-
A.
summitLatitude
Indicates the geographic latitude coordinate at which the summit or highest point of an entity is located.
-
B.
hasSummitLongitude
chosen
Indicates the longitudinal coordinate at which the summit or highest point of an entity is located.
-
C.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
-
D.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
E.
summitLocatedIn
Indicates that a summit (mountain peak) is geographically situated within a specified area or region.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.