Triple
T27068423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazda Kabura |
E685242
|
entity |
| Predicate | passengerSideDoorType |
P128223
|
FINISHED |
| Object | long front door with integrated rear access |
—
|
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: long front door with integrated rear access | Statement: [Mazda Kabura, passengerSideDoorType, long front door with integrated rear access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerSideDoorType Context triple: [Mazda Kabura, passengerSideDoorType, long front door with integrated rear access]
-
A.
vehicleDoorType
chosen
Indicates the specific style or configuration of doors that a vehicle has.
-
B.
hasDoorSide
Indicates that one entity represents a specific side or face of a door in relation to another entity.
-
C.
hasCargoDoorVariant
Indicates that one entity is a specific cargo-door-equipped version or configuration variant of another entity.
-
D.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
E.
hasRearHingedDoors
Indicates that the subject is equipped with doors whose hinges are located at the rear edge rather than the front.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 8:26 a.m.