Triple
T30234461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi S3 |
E768720
|
entity |
| Predicate | aboveInPerformanceRange |
P169011
|
FINISHED |
| Object | Audi RS3 |
—
|
NE NERFINISHED |
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: Audi RS3 | Statement: [Audi S3, aboveInPerformanceRange, Audi RS3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aboveInPerformanceRange Context triple: [Audi S3, aboveInPerformanceRange, Audi RS3]
-
A.
targetPerformanceLevel
Indicates the specific performance standard or level that an entity is expected or required to achieve.
-
B.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
C.
positionInPerformance
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
-
D.
performsWellOn
Indicates that one entity achieves good results or high performance when evaluated using, or operating within, another entity (such as a task, test, or environment).
-
E.
basedOnPerformanceBy
Indicates that something is derived from, adapted from, or determined according to the performance carried out by a particular entity.
- F. None of above. chosen
Provenance (4 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68048f7e481908c7b6e3788b04549 |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:37 p.m.