Triple
T825774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Meridian |
E17848
|
entity |
| Predicate | longitudeValue |
P1282
|
FINISHED |
| Object | 0° |
—
|
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: 0° | Statement: [Prime Meridian, longitudeValue, 0°]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longitudeValue Context triple: [Prime Meridian, longitudeValue, 0°]
-
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.
oppositeLatitude
Indicates that one entity is located at the same longitude as another but at the latitude that is equal in magnitude and opposite in sign (i.e., mirrored across the equator).
-
D.
distanceFromEquator
Indicates how far a location is from the Earth's equator, typically measured as a geographic or angular distance.
-
E.
reasonForLatitude
Indicates that one factor or circumstance serves as the explanation or cause for a particular degree or extent of latitude (freedom, variation, or deviation) in a situation or condition.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.