Triple
T16920069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chryse Planitia |
E410422
|
entity |
| Predicate | approximateCenterLatitude |
P1281
|
FINISHED |
| Object | about 28 degrees north |
—
|
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 28 degrees north | Statement: [Chryse Planitia, approximateCenterLatitude, about 28 degrees north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCenterLatitude Context triple: [Chryse Planitia, approximateCenterLatitude, about 28 degrees north]
-
A.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
B.
hasCoordinateInCityCentreApprox
Indicates that an entity’s location is approximately within the central area of a city, based on its geographic coordinates.
-
C.
nearestMajorCenter
Indicates that one location is the closest significant urban or population center relative to another location.
-
D.
coordinateLatitude
chosen
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
E.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cded2f8481909a20cc08b47e922e |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.