Triple
T18539401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peak Rail |
E453050
|
entity |
| Predicate | typicalTractionType |
P132066
|
FINISHED |
| Object | steam locomotives |
—
|
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: steam locomotives | Statement: [Peak Rail, typicalTractionType, steam locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTractionType Context triple: [Peak Rail, typicalTractionType, steam locomotives]
-
A.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
-
B.
currentTractionType
Indicates the type or mode of traction currently being applied or in use in a given context.
-
C.
typicalPickupType
Indicates the usual or standard method by which an item or order is collected or picked up.
-
D.
previousTractionType
Indicates the type of traction or traction method that was used previously before the current one.
-
E.
successorTractionType
Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b5863881908915a6762718d3f7 |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.