Triple
T4787673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | modified Volkswagen Touareg |
E106522
|
entity |
| Predicate | customizationType |
P31649
|
FINISHED |
| Object | performance modification |
—
|
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: performance modification | Statement: [modified Volkswagen Touareg, customizationType, performance modification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customizationType Context triple: [modified Volkswagen Touareg, customizationType, performance modification]
-
A.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
B.
custom
Indicates that something is specially created, configured, or tailored for a particular purpose, context, or user rather than being standard or generic.
-
C.
adjustmentType
chosen
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
-
D.
veilCustom
Indicates a customary or traditional practice involving the wearing or use of a veil.
-
E.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65da229c81909c703393f7b9b71d |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.