Triple
T28217264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E7 series |
E711345
|
entity |
| Predicate | powerSupplyToTrain |
P11313
|
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: [E7 series, powerSupplyToTrain, overhead line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSupplyToTrain Context triple: [E7 series, powerSupplyToTrain, overhead line]
-
A.
rollingStockPowerSupply
Indicates that one rolling stock entity provides or is associated with a specific power supply used to operate or support another entity.
-
B.
powering
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
C.
suppliesPowerTo
chosen
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
powerDistribution
Indicates how authority, control, or influence is allocated and shared among entities within a system or relationship.
-
E.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 10:43 p.m.