Triple
T417415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier M5000 |
E8024
|
entity |
| Predicate | powerCollectionMethod |
P14641
|
FINISHED |
| Object | overhead line |
—
|
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: overhead line | Statement: [Bombardier M5000, powerCollectionMethod, overhead line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerCollectionMethod Context triple: [Bombardier M5000, powerCollectionMethod, overhead line]
-
A.
currentCollectionMethod
Indicates the method or process currently being used to collect something (such as data, payments, or materials) from an entity.
-
B.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
C.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
D.
paymentMethod
Indicates the means or instrument through which a payment is made in a transaction.
-
E.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.