Triple
T35250334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 6 |
E1018076
|
entity |
| Predicate | inUniverseLaunchSite |
P4384
|
FINISHED |
| Object | Earth |
—
|
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: Earth | Statement: [Voyager 6, inUniverseLaunchSite, Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseLaunchSite Context triple: [Voyager 6, inUniverseLaunchSite, Earth]
-
A.
launchSiteInUniverse
Indicates that a launch site exists or is located within a particular universe or cosmic setting.
-
B.
usesLaunchSite
chosen
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
C.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
-
D.
inUniverseSystem
Indicates that one entity exists or operates within the scope, rules, or continuity of a particular fictional or conceptual universe or system.
-
E.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:02 p.m.