Triple
T26123045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen P. Synnott |
E659026
|
entity |
| Predicate | usedSpacecraftDataFrom |
P140424
|
FINISHED |
| Object | Voyager 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: Voyager 1 | Statement: [Stephen P. Synnott, usedSpacecraftDataFrom, Voyager 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSpacecraftDataFrom Context triple: [Stephen P. Synnott, usedSpacecraftDataFrom, Voyager 1]
-
A.
usedWithSpacecraft
Indicates that something is employed or operated in conjunction with a spacecraft.
-
B.
usedWithSpacecraftSeries
Indicates that something is employed or associated in use with a particular series or family of spacecraft.
-
C.
mainSpacecraft
Indicates that one spacecraft is designated as the primary or principal spacecraft in relation to another entity or context.
-
D.
backupSpacecraft
Indicates that one spacecraft serves as a backup or redundant counterpart for another spacecraft.
-
E.
associatedWithSpacecraft
chosen
Indicates a relationship in which an entity is connected or related in some way to a particular spacecraft, such as by operation, design, mission, or support role.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60acd4cdc8190bbb11e4171c685b0 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:09 p.m.