Triple
T31867789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alstom |
E813505
|
entity |
| Predicate | notableHydrogenTrain |
P1669
|
FINISHED |
| Object | Coradia iLint |
E763835
|
NE 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: Coradia iLint | Statement: [Alstom, notableHydrogenTrain, Coradia iLint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHydrogenTrain Context triple: [Alstom, notableHydrogenTrain, Coradia iLint]
-
A.
notableTrain
chosen
Indicates that there is a train or rail service associated with the subject that is considered notable or significant in some way.
-
B.
notableHybrid
Indicates that one entity is a hybrid of two or more distinct types, lineages, or categories and is recognized as notable or significant in that hybrid form.
-
C.
notableRailwayProject
Indicates that the subject is recognized for involvement in a significant or prominent railway-related project.
-
D.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
E.
notableTrainBrand
Indicates that an entity is a well-known or significant brand associated with trains or railway services.
- F. None of above.
Provenance (4 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e65bf0c608190af99c129817b129d |
completed | June 14, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:54 p.m.