Triple
T32366791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amundsen crater |
E827015
|
entity |
| Predicate | hasLatitude_deg |
P146432
|
FINISHED |
| Object | -84 |
—
|
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: -84 | Statement: [Amundsen crater, hasLatitude_deg, -84]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatitude_deg Context triple: [Amundsen crater, hasLatitude_deg, -84]
-
A.
coordinateLatitude
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.
landingLatitudeApprox
Indicates an approximate geographic latitude at which a landing event occurs.
-
D.
lunarLatitude
Indicates the angular distance of a point on the Moon north or south of the lunar equator.
-
E.
planetographicLatitude
chosen
Indicates the latitude of a location on a planetary body measured in a coordinate system tied to the planet’s figure and rotation (planetographic coordinates).
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 12:50 a.m.