Triple
T6170974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadillac Eldorado Brougham show car |
E137694
|
entity |
| Predicate | stylingType |
P35341
|
FINISHED |
| Object | futuristic |
—
|
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: futuristic | Statement: [Cadillac Eldorado Brougham show car, stylingType, futuristic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylingType Context triple: [Cadillac Eldorado Brougham show car, stylingType, futuristic]
-
A.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
B.
structuralStyle
chosen
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
C.
stylingEnables
Indicates that one entity provides or activates styling capabilities or visual formatting for another entity.
-
D.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
E.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d910c3c8190ae6af548259295ff |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.