Triple
T6963444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 700 |
E161427
|
entity |
| Predicate | constructionYears |
P44381
|
FINISHED |
| Object | 2014–2018 |
—
|
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: 2014–2018 | Statement: [British Rail Class 700, constructionYears, 2014–2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionYears Context triple: [British Rail Class 700, constructionYears, 2014–2018]
-
A.
productionYears
chosen
Indicates the span of calendar years during which something was produced or manufactured.
-
B.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
-
C.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
D.
modelYears
Indicates the association between a product (often a vehicle or device) and the specific calendar years in which that model version was produced or marketed.
-
E.
incorporationYear
Indicates the calendar year in which an organization or entity was formally incorporated or legally established.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf197b0819085bd0433c8a7f716 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.