Triple
T28693579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Touran |
E729351
|
entity |
| Predicate | hasFoldingRearSeats |
P72541
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Volkswagen Touran, hasFoldingRearSeats, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoldingRearSeats Context triple: [Volkswagen Touran, hasFoldingRearSeats, true]
-
A.
hasSlidingRearSeats
Indicates that an object features rear seats that can slide forward or backward to adjust space or seating position.
-
B.
hasRetractableSeating
chosen
Indicates that an entity is equipped with seating that can be folded away, collapsed, or otherwise retracted when not in use.
-
C.
hasRearHingedDoors
Indicates that the subject is equipped with doors whose hinges are located at the rear edge rather than the front.
-
D.
hasLevelingSeats
Indicates that an entity is equipped with seats whose positions can be adjusted or leveled relative to their surroundings.
-
E.
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.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 5:37 a.m.