Triple
T969805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE30AC locomotive |
E20919
|
entity |
| Predicate | hasControlType |
P6850
|
FINISHED |
| Object | push-pull cab control |
—
|
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: push-pull cab control | Statement: [DE30AC locomotive, hasControlType, push-pull cab control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlType Context triple: [DE30AC locomotive, hasControlType, push-pull cab control]
-
A.
typeOfControl
chosen
Indicates the specific manner or mechanism by which one entity exercises control or influence over another.
-
B.
hasInputType
Indicates that an entity takes another entity as its input type for its operation, function, or process.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
E.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4497d688190b59c3a195e377080 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.