Triple
T26170016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stardust |
E654373
|
entity |
| Predicate | visitedDuringExtendedMission |
P26942
|
FINISHED |
| Object | Comet 9P/Tempel 1 |
—
|
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: Comet 9P/Tempel 1 | Statement: [Stardust, visitedDuringExtendedMission, Comet 9P/Tempel 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedDuringExtendedMission Context triple: [Stardust, visitedDuringExtendedMission, Comet 9P/Tempel 1]
-
A.
visitedDuring
chosen
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
B.
exploredDuring
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
C.
carriedOutMissionIn
Indicates that an entity performed or executed a specific mission in a particular context or location.
-
D.
hadMission
Indicates that an entity (such as a person, organization, or vehicle) was assigned or carried out a specific mission or operation.
-
E.
visitedWith
Indicates that one entity visited a place or another entity together with a companion entity during the same occasion.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c425de88190a221b40e81d0dcc1 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:34 p.m.