Triple
T35250335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 6 |
E1018076
|
entity |
| Predicate | inUniverseMissionType |
P192009
|
FINISHED |
| Object | deep-space probe |
—
|
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: deep-space probe | Statement: [Voyager 6, inUniverseMissionType, deep-space probe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseMissionType Context triple: [Voyager 6, inUniverseMissionType, deep-space probe]
-
A.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
B.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
C.
inUniverseSystem
Indicates that one entity exists or operates within the scope, rules, or continuity of a particular fictional or conceptual universe or system.
-
D.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
E.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: May 3, 2026, 4:02 p.m.