Triple
T17474938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isidis Planitia |
E425514
|
entity |
| Predicate | centerLatitude |
P1281
|
FINISHED |
| Object | approximately 12°N |
—
|
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: approximately 12°N | Statement: [Isidis Planitia, centerLatitude, approximately 12°N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerLatitude Context triple: [Isidis Planitia, centerLatitude, approximately 12°N]
-
A.
coordinateLatitude
chosen
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
B.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
C.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
D.
homeCityLatitude
Indicates the geographic latitude coordinate associated with an entity’s home city.
-
E.
intendedLongitude
Indicates the longitude value that an entity is meant or planned to have or reach, rather than its actual current longitude.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451baa7b0819092035fec42305397 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.