Triple
T16470865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class 5MT |
E400054
|
entity |
| Predicate | locomotiveWheelArrangement |
P77781
|
FINISHED |
| Object | 4-6-0 |
—
|
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: 4-6-0 | Statement: [Class 5MT, locomotiveWheelArrangement, 4-6-0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotiveWheelArrangement Context triple: [Class 5MT, locomotiveWheelArrangement, 4-6-0]
-
A.
locomotiveWheelArrangementStandard
Indicates the standard classification system used to describe the wheel arrangement of a locomotive.
-
B.
locomotiveConfiguration
chosen
Indicates the specific arrangement and type of power and running units (e.g., wheel or axle layout) that define how a locomotive is configured.
-
C.
typicalLocomotiveClass
Indicates that one locomotive class is the standard or most commonly used class for a given context, operator, or service.
-
D.
railcode
Indicates that an entity is associated with a specific railway code used for identification or classification within a rail system.
-
E.
laterLocomotiveType
Indicates that one locomotive type succeeds or comes after another in time, representing a later development or version in locomotive design.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd0d2fc81909b68b5afb00f192f |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.