Triple
T4614912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Railways |
E100843
|
entity |
| Predicate | secondaryFuelType |
P22119
|
FINISHED |
| Object | diesel traction |
—
|
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: diesel traction | Statement: [Indian Railways, secondaryFuelType, diesel traction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryFuelType Context triple: [Indian Railways, secondaryFuelType, diesel traction]
-
A.
fuelRole
Indicates that one entity serves as the fuel or energy source used or consumed by another entity in a process or operation.
-
B.
previousFuelType
Indicates that an entity was formerly associated with or used a specified type of fuel before a change to a different fuel type.
-
C.
typicalFuel
chosen
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
-
D.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
E.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59c3d9ec8190a50ef03627dc351d |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.