Triple
T17287399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPI MP36PH-3C |
E419693
|
entity |
| Predicate | headEndPowerType |
P126819
|
FINISHED |
| Object | separate HEP generator |
—
|
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: separate HEP generator | Statement: [MPI MP36PH-3C, headEndPowerType, separate HEP generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headEndPowerType Context triple: [MPI MP36PH-3C, headEndPowerType, separate HEP generator]
-
A.
headEndPower
Indicates that one entity supplies electrical power from the front (head end) of a train to other connected railcars or systems.
-
B.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
C.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
-
D.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
E.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43780fad88190b82193c8335e2f11 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.