Triple
T27467631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Hills |
E693216
|
entity |
| Predicate | imagedByOrbiter |
P162660
|
FINISHED |
| Object | Mars Global Surveyor |
—
|
NE NERFINISHED |
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: Mars Global Surveyor | Statement: [Columbia Hills, imagedByOrbiter, Mars Global Surveyor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imagedByOrbiter Context triple: [Columbia Hills, imagedByOrbiter, Mars Global Surveyor]
-
A.
imagedByOrbiter
chosen
Indicates that an entity has been captured or recorded in an image taken by an orbiting spacecraft or satellite.
-
B.
orbiterNumber
Indicates the identifying number assigned to a specific orbiter associated with an object or mission.
-
C.
discoveredBySpacecraft
Indicates that something was first detected, observed, or found as a result of a spacecraft’s instruments or mission activities.
-
D.
orbiterType
Indicates the specific class or category of an orbiter based on its design, mission role, or operational characteristics.
-
E.
notableOrbiter
Indicates that one entity is a particularly significant or well-known artificial satellite or spacecraft that orbits another entity.
- 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_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 12:52 p.m.