Triple
T20748296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMD SD70 series locomotives |
E510645
|
entity |
| Predicate | typicalHorsepowerRange |
P65190
|
FINISHED |
| Object | 4000–4500 hp |
—
|
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: 4000–4500 hp | Statement: [EMD SD70 series locomotives, typicalHorsepowerRange, 4000–4500 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHorsepowerRange Context triple: [EMD SD70 series locomotives, typicalHorsepowerRange, 4000–4500 hp]
-
A.
powerRange
chosen
Indicates the range of power values within which an entity operates, applies, or is considered valid.
-
B.
horsepower
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
C.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
typicalPower
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c226fbf881909794eff3ee9e206b |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:33 p.m.