Triple
T38054773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship (SpaceX) |
E949868
|
entity |
| Predicate | notableMissionPlanned |
P42909
|
FINISHED |
| Object | dearMoon circumlunar mission (status uncertain) |
E2007260
|
NE FINISHED |
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: dearMoon circumlunar mission (status uncertain) | Statement: [Starship (SpaceX), notableMissionPlanned, dearMoon circumlunar mission (status uncertain)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMissionPlanned Context triple: [Starship (SpaceX), notableMissionPlanned, dearMoon circumlunar mission (status uncertain)]
-
A.
notableMissionLaunched
Indicates that an entity (such as a space agency or organization) has launched a mission that is considered notable or significant.
-
B.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
C.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
D.
intendedMission
chosen
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
spacecraftPlanned
Indicates that a spacecraft is scheduled or intended to be launched, operated, or utilized in the future according to a plan or mission design.
- F. None of above.
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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d3315e8819088a67cce7ec138e7 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.