Triple
T27873683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE U-series locomotives |
E704867
|
entity |
| Predicate | wheelArrangementVariants |
P163970
|
FINISHED |
| Object | B-B |
—
|
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: B-B | Statement: [GE U-series locomotives, wheelArrangementVariants, B-B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelArrangementVariants Context triple: [GE U-series locomotives, wheelArrangementVariants, B-B]
-
A.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
B.
includesWheelArrangement
Indicates that one entity possesses or features a particular configuration or arrangement of wheels.
-
C.
hasLeadingWheelArrangement
Indicates the specific configuration of the leading (front) wheels in a vehicle’s or locomotive’s wheel arrangement.
-
D.
hasTrailingWheelArrangement
Indicates that an entity (typically a vehicle) possesses a specific configuration of wheels located at its rear or trailing end.
-
E.
wheelType
Indicates the specific kind or category of wheel associated with an entity.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 6:26 p.m.