Triple
T20577687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Envoy SLE |
E505264
|
entity |
| Predicate | featureLevelComparedToHigherTrims |
P28765
|
FINISHED |
| Object | fewer luxury features |
—
|
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: fewer luxury features | Statement: [Envoy SLE, featureLevelComparedToHigherTrims, fewer luxury features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureLevelComparedToHigherTrims Context triple: [Envoy SLE, featureLevelComparedToHigherTrims, fewer luxury features]
-
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.
includesVehicleLevel
Indicates that something encompasses or applies to a specific level or category associated with a vehicle.
-
C.
comparisonLevel
Indicates the degree or intensity to which two or more entities are being compared within a given context.
-
D.
offersTrimLevel
Indicates that a product or model is available in a specific trim level or configuration option.
-
E.
hasLevelingSeats
Indicates that an entity is equipped with seats whose positions can be adjusted or leveled relative to their surroundings.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a90bbcfc81909ca4cab8038c634b |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.