Triple
T21698828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2.5-litre Busso V6 |
E535598
|
entity |
| Predicate | layoutInVehicles |
P5253
|
FINISHED |
| Object | front-engine |
—
|
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: front-engine | Statement: [2.5-litre Busso V6, layoutInVehicles, front-engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutInVehicles Context triple: [2.5-litre Busso V6, layoutInVehicles, front-engine]
-
A.
vehicleLayout
chosen
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
B.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
C.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
D.
vehicleToLoad
Indicates a relationship where a vehicle is associated with, assigned to, or responsible for transporting a particular load.
-
E.
vehicleLoadingMethod
Indicates the method or process by which a vehicle is loaded with goods, passengers, or other cargo.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b7de9888190bbca7717a32f9888 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.