Triple
T27467629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Hills |
E693216
|
entity |
| Predicate | visitedByRoverSolRange |
P62441
|
FINISHED |
| Object | Spirit sols ~150–800 |
—
|
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: Spirit sols ~150–800 | Statement: [Columbia Hills, visitedByRoverSolRange, Spirit sols ~150–800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedByRoverSolRange Context triple: [Columbia Hills, visitedByRoverSolRange, Spirit sols ~150–800]
-
A.
exploredBySpacecraft
chosen
Indicates that a celestial object or region has been visited, observed, or studied directly by a spacecraft.
-
B.
positionOnPerseverance
Indicates that one entity occupies a specific physical location or mounting point on the Perseverance rover.
-
C.
firstOperationDateOnMars
Indicates the date on which the very first operation or activity was carried out on Mars.
-
D.
discoveredBySpacecraft
Indicates that something was first detected, observed, or found as a result of a spacecraft’s instruments or mission activities.
-
E.
orbitsCompletedAroundMars
Indicates the number of full orbital revolutions an object has completed around Mars.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfe6f7881909a45a89d1b753b1a |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:52 p.m.