Triple
T330073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadillac Escalade |
E6605
|
entity |
| Predicate | notableReputation |
P22
|
FINISHED |
| Object | status symbol in North America |
—
|
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: status symbol in North America | Statement: [Cadillac Escalade, notableReputation, status symbol in North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableReputation Context triple: [Cadillac Escalade, notableReputation, status symbol in North America]
-
A.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
C.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
D.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
-
E.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaaeb64881909c7ab9bca3378e2b |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94aab1c8190b8654708c87eeb91 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.