Triple
T21572268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterCity 225 |
E532312
|
entity |
| Predicate | tractionVoltage |
P144303
|
FINISHED |
| Object | 25 kV AC overhead |
—
|
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: 25 kV AC overhead | Statement: [InterCity 225, tractionVoltage, 25 kV AC overhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tractionVoltage Context triple: [InterCity 225, tractionVoltage, 25 kV AC overhead]
-
A.
tractionPower
Indicates the amount of mechanical or electrical power available or used to provide tractive force for movement or propulsion.
-
B.
volta
Indicates a turning or change of direction, such as a shift in movement, course, or focus between entities.
-
C.
controlledByVoltageBetween
Indicates that the behavior or state of one entity is regulated or determined by the electrical potential difference (voltage) between two other entities.
-
D.
symbolForVoltage
Indicates that one entity is the symbolic representation used to denote the voltage associated with another entity.
-
E.
affectedByVoltAbsorb
Indicates that an entity is impacted by the Volt Absorb effect, typically converting incoming electric-based effects into a beneficial outcome rather than taking damage.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cd50188190b44eb25fb87312bb |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.