Triple
T15637432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTC−11 time zone |
E375981
|
entity |
| Predicate | typicalLongitudeCenter |
P1282
|
FINISHED |
| Object | about 165°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: about 165°W | Statement: [UTC−11 time zone, typicalLongitudeCenter, about 165°W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLongitudeCenter Context triple: [UTC−11 time zone, typicalLongitudeCenter, about 165°W]
-
A.
typicalCityLongitude
Indicates the standard or representative longitude value associated with a given city.
-
B.
typicalCityLatitude
Indicates the usual or representative latitude at which a given city is located.
-
C.
intendedLongitude
Indicates the longitude value that an entity is meant or planned to have or reach, rather than its actual current longitude.
-
D.
coordinateLongitude
chosen
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
E.
geographicCenter
Indicates the location that serves as the central point of a geographic 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.