Triple
T29329065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rubber duck comet |
E743728
|
entity |
| Predicate | RosettaEndOfMission |
P41474
|
FINISHED |
| Object | 2016-09-30 |
—
|
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: 2016-09-30 | Statement: [rubber duck comet, RosettaEndOfMission, 2016-09-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RosettaEndOfMission Context triple: [rubber duck comet, RosettaEndOfMission, 2016-09-30]
-
A.
finalMercuryMission
Indicates that an event or mission is the last or concluding mission in the Mercury program.
-
B.
RosettaArrivalDate
Indicates the date on which the Rosetta spacecraft arrives at or reaches its designated target.
-
C.
newLocationOfPhilae
Indicates the relationship where a specified place or position is the new, subsequent location of Philae after it has moved or been relocated.
-
D.
missionEnd
chosen
Indicates that a mission has concluded or reached its final state or outcome.
-
E.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6689891608190a721be24599c4edd |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:28 p.m.