Triple
T27340388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jocotepec |
E690079
|
entity |
| Predicate | locatedInLongitudeRange |
P23540
|
FINISHED |
| Object | Western Hemisphere |
—
|
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: Western Hemisphere | Statement: [Jocotepec, locatedInLongitudeRange, Western Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLongitudeRange Context triple: [Jocotepec, locatedInLongitudeRange, Western Hemisphere]
-
A.
regionLongitudeRange
chosen
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
B.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
C.
visibleAtLatitudeBetween
Indicates that something can be seen or is observable only within a specified range of latitudes.
-
D.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
E.
basedOnLongitudeOf
Indicates that one entity’s position, value, or determination is derived from or defined with respect to the longitude of another entity.
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: April 27, 2026, 11:42 a.m.