Triple
T15598614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Energy Spectroscopic Instrument |
E374970
|
entity |
| Predicate | plannedSurveyDuration |
P40755
|
FINISHED |
| Object | 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: 5 years | Statement: [Dark Energy Spectroscopic Instrument, plannedSurveyDuration, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedSurveyDuration Context triple: [Dark Energy Spectroscopic Instrument, plannedSurveyDuration, 5 years]
-
A.
surveyDuration
Indicates the length of time over which a survey is conducted or remains active.
-
B.
intendedDuration
chosen
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
C.
surveyCadence
Indicates how frequently or at what regular interval surveys are conducted or sent out.
-
D.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
E.
durationPerParticipant
Indicates the amount of time associated with or allocated to each individual participant in the related activity or event.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e609ab081909feb486a57439960 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.