Triple
T31867777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alstom |
E813505
|
entity |
| Predicate | acquisitionOfBombardierTransportationCompleted |
P15703
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Alstom, acquisitionOfBombardierTransportationCompleted, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfBombardierTransportationCompleted Context triple: [Alstom, acquisitionOfBombardierTransportationCompleted, 2021]
-
A.
acquiredByCanada
Indicates that an entity was obtained, purchased, or otherwise brought under the ownership or control of Canada.
-
B.
completedTranscontinentalLine
Indicates that an entity has finished constructing or establishing a railway or transportation line that spans an entire continent.
-
C.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
-
D.
laterAcquiredBy
Indicates that one entity was acquired by another entity at a later point in time, after some prior state or ownership.
-
E.
acquisitionCompletedYear
chosen
Indicates the calendar year in which an acquisition transaction was fully completed.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 11:54 p.m.