Triple
T8326977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Golf Sportsvan |
E194977
|
entity |
| Predicate | interiorSpace |
P26940
|
FINISHED |
| Object | increased compared to standard Volkswagen Golf |
—
|
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: increased compared to standard Volkswagen Golf | Statement: [Volkswagen Golf Sportsvan, interiorSpace, increased compared to standard Volkswagen Golf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorSpace Context triple: [Volkswagen Golf Sportsvan, interiorSpace, increased compared to standard Volkswagen Golf]
-
A.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
B.
interiorFloor
Indicates that one entity is the interior floor surface or flooring of another enclosing space or structure.
-
C.
interiorSize
chosen
Indicates the size or dimensions of the inside space of an object or structure.
-
D.
spaceType
Indicates the category or kind of physical or conceptual space associated with an entity.
-
E.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f80ed288190b300e18b9bc58824 |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.