Triple
T12919431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WM Class I-2 2-10-0 |
E309074
|
entity |
| Predicate | tractionCharacteristic |
P19787
|
FINISHED |
| Object | high tractive effort |
—
|
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: high tractive effort | Statement: [WM Class I-2 2-10-0, tractionCharacteristic, high tractive effort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tractionCharacteristic Context triple: [WM Class I-2 2-10-0, tractionCharacteristic, high tractive effort]
-
A.
tailCharacteristic
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
-
B.
tractionType
chosen
Indicates the type or method of traction applied or used in relation to an entity or system.
-
C.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
D.
trimCharacteristic
Indicates that one entity defines or specifies a trimming-related property or feature of another entity.
-
E.
tractionPower
Indicates the amount of mechanical or electrical power available or used to provide tractive force for movement or propulsion.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e6d9fc8190b8a5244b26b5f78a |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.