Triple
T27068418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazda Kabura |
E685242
|
entity |
| Predicate | seatingLayout |
P16826
|
FINISHED |
| Object | 3+1 seating layout |
—
|
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: 3+1 seating layout | Statement: [Mazda Kabura, seatingLayout, 3+1 seating layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingLayout Context triple: [Mazda Kabura, seatingLayout, 3+1 seating layout]
-
A.
seatingConfiguration
chosen
Indicates how seats are arranged or organized relative to each other in a given context.
-
B.
seatingDirection
Indicates the orientation or facing direction in which an entity is seated relative to a reference point or object.
-
C.
hasFlexibleSeating
Indicates that an entity provides seating arrangements that can be easily rearranged, adjusted, or reconfigured to suit different uses or preferences.
-
D.
individualSeats
Indicates that an entity provides or consists of separate, single-person seating positions rather than shared or bench-style seating.
-
E.
seatingPosition
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 8:26 a.m.