Triple
T45805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilean Antarctic Territory |
E897
|
entity |
| Predicate | westernBoundaryLongitude |
P1282
|
FINISHED |
| Object | 90°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: 90°W | Statement: [Chilean Antarctic Territory, westernBoundaryLongitude, 90°W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernBoundaryLongitude Context triple: [Chilean Antarctic Territory, westernBoundaryLongitude, 90°W]
-
A.
coordinateLongitude
chosen
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
B.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
C.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
D.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
-
E.
adjacentTimeZoneWest
Indicates that one time zone is directly to the west of another, sharing a common boundary without any other time zone in between.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24abbd32c81908cec461d9097662e |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.