Triple
T26509821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESO ELT |
E669647
|
entity |
| Predicate | firstLightPlanned |
P14088
|
FINISHED |
| Object | late 2020s |
—
|
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: late 2020s | Statement: [ESO ELT, firstLightPlanned, late 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLightPlanned Context triple: [ESO ELT, firstLightPlanned, late 2020s]
-
A.
expectedFirstLight
chosen
Indicates the anticipated time or occurrence of the first appearance of light, such as dawn or initial illumination, in a given context.
-
B.
firstLightYear
Indicates the specific light-year distance at which something first occurs, begins, or is measured.
-
C.
firstLightingYear
Indicates the year in which something (such as a light source or lighting installation) was first put into operation or illuminated.
-
D.
firstLightOfVLT
Indicates the event or moment when the Very Large Telescope (VLT) successfully captured its first astronomical light (initial operational observation).
-
E.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 27, 2026, 1:19 a.m.