Triple
T13526074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Publica |
E323018
|
entity |
| Predicate | doorLayout |
P4168
|
FINISHED |
| Object | front-hinged doors |
—
|
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-hinged doors | Statement: [Toyota Publica, doorLayout, front-hinged doors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorLayout Context triple: [Toyota Publica, doorLayout, front-hinged doors]
-
A.
doorLocation
Indicates the spatial position or placement of a door relative to a reference structure or area.
-
B.
doorConfiguration
chosen
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
C.
floorPlan
Indicates that one entity serves as the architectural layout or room arrangement blueprint for another entity (such as a building or space).
-
D.
wallPlan
Indicates a planned or designed configuration of walls within a space or structure.
-
E.
doorType
Indicates the specific kind or category of door associated with an 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa6ad60819087824e4ac83934ed |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.