Triple
T24190902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier Turbostar multiple units |
E599690
|
entity |
| Predicate | hasBuilderPredecessor |
P155620
|
FINISHED |
| Object | Adtranz |
—
|
NE NERFINISHED |
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: Adtranz | Statement: [Bombardier Turbostar multiple units, hasBuilderPredecessor, Adtranz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuilderPredecessor Context triple: [Bombardier Turbostar multiple units, hasBuilderPredecessor, Adtranz]
-
A.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
-
B.
hasPredecessorType
Indicates that one type is derived from, follows, or is based on another earlier or more fundamental type in a sequence or hierarchy.
-
C.
hasPredecessorGeneration
Indicates that one generation directly precedes another in a temporal or genealogical sequence.
-
D.
hasPredecessorMP
Indicates that one member of parliament previously held the same parliamentary position or seat before another member of parliament.
-
E.
calledPredecessorOf
Indicates that one entity is referred to or designated as the predecessor of another entity.
- F. None of above. chosen
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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 17, 2026, 11:35 p.m.