Triple
T36705723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOM camera |
E906354
|
entity |
| Predicate | orbitsBodyWithHostMission |
P54198
|
FINISHED |
| Object | Mars |
—
|
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 | Statement: [MOM camera, orbitsBodyWithHostMission, Mars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsBodyWithHostMission Context triple: [MOM camera, orbitsBodyWithHostMission, Mars]
-
A.
orbitsPrimaryViaHostBody
chosen
Indicates that an object orbits its primary body indirectly by orbiting an intermediate host body which itself orbits that primary.
-
B.
orbitsWithParentBody
Indicates that one body orbits another while explicitly maintaining a reference to its primary or parent body in the orbital relationship.
-
C.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
D.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
E.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.