Triple
T395495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 2 |
E8973
|
entity |
| Predicate | NeptuneFlybyDate |
P12572
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Voyager 2, NeptuneFlybyDate, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NeptuneFlybyDate Context triple: [Voyager 2, NeptuneFlybyDate, 1989]
-
A.
firstSuccessfulFlybyBy
Indicates that the subject is the first spacecraft or mission to successfully perform a flyby of the object specified by the predicate’s value.
-
B.
closestApproachToJupiterDate
Indicates the date on which an object reaches its minimum distance from Jupiter during its trajectory or orbit.
-
C.
closestApproachToSaturnDate
Indicates the date on which an object reaches its minimum distance from Saturn during its trajectory or observation period.
-
D.
enteredInterstellarSpaceDate
Indicates the date on which an object or entity crossed the boundary of its originating stellar system and entered interstellar space.
-
E.
discoveryDateOfTitan
Indicates the date on which the celestial body Titan was first discovered or identified.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec792dd081909b6b18a854139f8c |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.