Triple
T364152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope |
E7921
|
entity |
| Predicate | missionDurationPlanned |
P12743
|
FINISHED |
| Object | 15 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: 15 years | Statement: [Hubble Space Telescope, missionDurationPlanned, 15 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDurationPlanned Context triple: [Hubble Space Telescope, missionDurationPlanned, 15 years]
-
A.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
B.
missionProfile
Indicates the specific set of objectives, conditions, and operational parameters that define how a mission is planned, conducted, and evaluated.
-
C.
missionCadence
Indicates the frequency or regular interval at which missions are planned, launched, or conducted.
-
D.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
E.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eafc8da88190b4a05182f4384442 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.