Triple
T31494201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sharp |
E803489
|
entity |
| Predicate | orbitalImagingBy |
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: [Mount Sharp, orbitalImagingBy, Mars Reconnaissance Orbiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalImagingBy Context triple: [Mount Sharp, orbitalImagingBy, Mars Reconnaissance Orbiter]
-
A.
imagedByOrbiter
chosen
Indicates that an entity has been captured or recorded in an image taken by an orbiting spacecraft or satellite.
-
B.
orbitalDetectionBy
Indicates that an orbital object or phenomenon is detected, observed, or measured by a specified instrument, sensor, or detection system.
-
C.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
orbitalPosition
Indicates the relative location or path of one object in its orbit with respect to a central body or reference frame.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e76f98819084babaa80607b5ed |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:40 p.m.