Triple
T20479608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawn |
E502415
|
entity |
| Predicate | discoveryProgramMissionNumber |
P26361
|
FINISHED |
| Object | ninth Discovery mission |
—
|
LITERAL 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: ninth Discovery mission | Statement: [Dawn, discoveryProgramMissionNumber, ninth Discovery mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryProgramMissionNumber Context triple: [Dawn, discoveryProgramMissionNumber, ninth Discovery mission]
-
A.
missionNumber
chosen
Indicates the identifying number assigned to a specific mission within a sequence or set of missions.
-
B.
missionID
Indicates a unique identifier that associates an entity with a specific mission or operation.
-
C.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
D.
discoveredBySpacecraft
Indicates that something was first detected, observed, or found as a result of a spacecraft’s instruments or mission activities.
-
E.
notableMissionLaunched
Indicates that an entity (such as a space agency or organization) has launched a mission that is considered notable or significant.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b55d7a881909dfe3ea0e74b742b |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.