Triple
T30142936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi A8 D5 |
E766174
|
entity |
| Predicate | performanceUpdate |
P141113
|
FINISHED |
| Object | improved efficiency over predecessors |
—
|
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: improved efficiency over predecessors | Statement: [Audi A8 D5, performanceUpdate, improved efficiency over predecessors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceUpdate Context triple: [Audi A8 D5, performanceUpdate, improved efficiency over predecessors]
-
A.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
B.
performanceAs
Indicates that one entity serves in a particular role, character, or capacity within a performance or presentation involving another entity.
-
C.
performanceOutcome
chosen
Indicates the result, effect, or consequence produced by a particular performance or action.
-
D.
performanceImprovementReason
Indicates the reason or cause behind an observed or intended improvement in performance.
-
E.
performanceVariable
Indicates that one entity represents a measurable factor or parameter that influences or characterizes the performance of another 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 7:18 p.m.