Triple
T197971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 1 |
E4038
|
entity |
| Predicate | expectedEndOfScienceOperations |
P6603
|
FINISHED |
| Object | in the 2030s |
—
|
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: in the 2030s | Statement: [Voyager 1, expectedEndOfScienceOperations, in the 2030s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedEndOfScienceOperations Context triple: [Voyager 1, expectedEndOfScienceOperations, in the 2030s]
-
A.
scienceGoals
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
B.
positionOnScience
Indicates the stance, viewpoint, or attitude an entity holds regarding science or scientific matters.
-
C.
chiefScientist
Indicates that one entity serves as the primary or lead scientist for another entity, typically holding top scientific authority or responsibility.
-
D.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
E.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.