Triple
T551940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LHC injector chain |
E11858
|
entity |
| Predicate | commissioningStartYear |
P6782
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [LHC injector chain, commissioningStartYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissioningStartYear Context triple: [LHC injector chain, commissioningStartYear, 2005]
-
A.
commissionedYear
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
-
B.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
-
C.
commissionedAt
chosen
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
D.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
E.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499047bd4819089ca8345f1b6e46c |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.