Triple
T29203550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alstom Class 460 |
E740345
|
entity |
| Predicate | rebuildProgrammePeriod |
P44073
|
FINISHED |
| Object | early 2010s |
—
|
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 2010s | Statement: [Alstom Class 460, rebuildProgrammePeriod, early 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildProgrammePeriod Context triple: [Alstom Class 460, rebuildProgrammePeriod, early 2010s]
-
A.
rebuildPeriodEnd
Indicates the point in time when a rebuilding or reconstruction process is scheduled or expected to be completed.
-
B.
rebuildPeriod
chosen
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
C.
reconstructionProgram
Indicates a program or initiative designed to rebuild, restore, or structurally improve something that has been damaged, degraded, or is otherwise in need of renewal.
-
D.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
E.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:08 p.m.