Triple
T30713044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VarioFlex rear seats |
E781942
|
entity |
| Predicate | allowsConfiguration |
P273
|
FINISHED |
| Object | 2-seat rear layout |
—
|
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: 2-seat rear layout | Statement: [VarioFlex rear seats, allowsConfiguration, 2-seat rear layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsConfiguration Context triple: [VarioFlex rear seats, allowsConfiguration, 2-seat rear layout]
-
A.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
-
B.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
C.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
D.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
E.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:35 p.m.