Triple
T33940271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 1 electrical power subsystem |
E870144
|
entity |
| Predicate | lifetimeDesignGoal |
P177944
|
FINISHED |
| Object | at least 5 years |
—
|
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: at least 5 years | Statement: [Voyager 1 electrical power subsystem, lifetimeDesignGoal, at least 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeDesignGoal Context triple: [Voyager 1 electrical power subsystem, lifetimeDesignGoal, at least 5 years]
-
A.
overallDesignGoal
Indicates that one entity specifies or represents the primary design objective or guiding design intent for another entity.
-
B.
goalOfLiving
Indicates that something represents the primary purpose, aim, or ultimate objective guiding a being’s life or existence.
-
C.
benefitDesignGoal
Indicates that something contributes positively toward achieving a particular design goal.
-
D.
urbanDesignGoal
Indicates a goal or intended outcome related to the planning, shaping, or improvement of urban spaces and environments.
-
E.
goalOfRealization
Indicates the intended outcome or objective that an action, process, or plan is meant to bring into reality or achieve.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.