Triple
T30142601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi RS models |
E766167
|
entity |
| Predicate | performanceLevelComparedToAudiS |
P28765
|
FINISHED |
| Object | higher |
—
|
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: higher | Statement: [Audi RS models, performanceLevelComparedToAudiS, higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceLevelComparedToAudiS Context triple: [Audi RS models, performanceLevelComparedToAudiS, higher]
-
A.
featureLevelComparedTo
chosen
Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
-
B.
comparisonLevel
Indicates the degree or intensity to which two or more entities are being compared within a given context.
-
C.
SAELevel
Indicates the level or degree of a subject according to the SAE (e.g., standard, classification, or grading) scale.
-
D.
performanceSubBrand
Indicates a relationship where a sub-brand is positioned or marketed as a higher-performance or performance-focused line within a main brand.
-
E.
statusRelativeToCadillac
Indicates how something is positioned, ranked, or evaluated in comparison to a Cadillac.
- 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_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 29, 2026, 7:18 p.m.