Triple
T38429453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D400–D449 |
E903757
|
entity |
| Predicate | tractionClass |
P190869
|
FINISHED |
| Object | Type 4 diesel |
—
|
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: Type 4 diesel | Statement: [D400–D449, tractionClass, Type 4 diesel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tractionClass Context triple: [D400–D449, tractionClass, Type 4 diesel]
-
A.
tractionType
Indicates the type or method of traction applied or used in relation to an entity or system.
-
B.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
C.
clase
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
-
D.
tractionPower
Indicates the amount of mechanical or electrical power available or used to provide tractive force for movement or propulsion.
-
E.
displacementClass
Indicates the category or type of physical displacement associated with an entity or event, typically grouping similar kinds or magnitudes of movement into a common class.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.