Triple
T3567709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadillac XLR-V |
E75490
|
entity |
| Predicate | performanceRole |
P268
|
FINISHED |
| Object | flagship performance model of the XLR line |
—
|
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: flagship performance model of the XLR line | Statement: [Cadillac XLR-V, performanceRole, flagship performance model of the XLR line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceRole Context triple: [Cadillac XLR-V, performanceRole, flagship performance model of the XLR line]
-
A.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
B.
displayRole
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
-
C.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
D.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0ab51d881908f004fae47ab09d9 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.