Triple
T2831038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Extremely Large Telescope |
E62234
|
entity |
| Predicate | designPhaseStart |
P11886
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [European Extremely Large Telescope, designPhaseStart, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPhaseStart Context triple: [European Extremely Large Telescope, designPhaseStart, early 2000s]
-
A.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
B.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
-
C.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
D.
developmentStart
chosen
Indicates the point in time or event when the development process of something begins.
-
E.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebd5a2c81908f0e30a0ae0eb8df |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.