Triple
T27068419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazda Kabura |
E685242
|
entity |
| Predicate | frontPassengerSeatPosition |
P22103
|
FINISHED |
| Object | slightly forward of driver seat |
—
|
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: slightly forward of driver seat | Statement: [Mazda Kabura, frontPassengerSeatPosition, slightly forward of driver seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontPassengerSeatPosition Context triple: [Mazda Kabura, frontPassengerSeatPosition, slightly forward of driver seat]
-
A.
seatingPosition
chosen
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
B.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
C.
seatRecline
Indicates that one entity adjusts or is capable of adjusting the backward tilt or reclining position of a seat relative to another entity or context.
-
D.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
E.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 8:26 a.m.