Triple
T330061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadillac Escalade |
E6605
|
entity |
| Predicate | trimLevel |
P11486
|
FINISHED |
| Object | Luxury |
—
|
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: Luxury | Statement: [Cadillac Escalade, trimLevel, Luxury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trimLevel Context triple: [Cadillac Escalade, trimLevel, Luxury]
-
A.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
B.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
C.
bodyLevel
Indicates the relative position or height of an entity’s body (or body part) along a vertical or hierarchical scale.
-
D.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
E.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
- 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_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. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.