Triple
T27467630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Hills |
E693216
|
entity |
| Predicate | imagedByOrbiter |
P162660
|
FINISHED |
| Object | Mars Reconnaissance Orbiter |
—
|
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 Reconnaissance Orbiter | Statement: [Columbia Hills, imagedByOrbiter, Mars Reconnaissance Orbiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imagedByOrbiter Context triple: [Columbia Hills, imagedByOrbiter, Mars Reconnaissance Orbiter]
-
A.
orbiterNumber
Indicates the identifying number assigned to a specific orbiter associated with an object or mission.
-
B.
discoveredBySpacecraft
Indicates that something was first detected, observed, or found as a result of a spacecraft’s instruments or mission activities.
-
C.
orbiterType
Indicates the specific class or category of an orbiter based on its design, mission role, or operational characteristics.
-
D.
notableOrbiter
Indicates that one entity is a particularly significant or well-known artificial satellite or spacecraft that orbits another entity.
-
E.
orbiterName
Indicates the name assigned to an orbiter associated with a particular mission or celestial body.
- F. None of above. chosen
Provenance (4 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_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 12:52 p.m.