Triple
T36486323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandra’s Altitudinal Composition Explorer |
E898941
|
entity |
| Predicate | missionBody |
P189486
|
FINISHED |
| Object | Moon |
—
|
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: Moon | Statement: [Chandra’s Altitudinal Composition Explorer, missionBody, Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionBody Context triple: [Chandra’s Altitudinal Composition Explorer, missionBody, Moon]
-
A.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
B.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
C.
missionOnEarth
Indicates that an entity has a mission, assignment, or purpose specifically taking place on Earth.
-
D.
missionPatch
Indicates that an entity serves as the official emblem or insignia associated with a particular mission.
-
E.
missionID
Indicates a unique identifier that associates an entity with a specific mission or operation.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:10 p.m.