Triple
T6787336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Expedition |
E155842
|
entity |
| Predicate | hasTrimLevels |
P55815
|
FINISHED |
| Object | multiple trims including base and luxury-oriented trims |
—
|
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: multiple trims including base and luxury-oriented trims | Statement: [Ford Expedition, hasTrimLevels, multiple trims including base and luxury-oriented trims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrimLevels Context triple: [Ford Expedition, hasTrimLevels, multiple trims including base and luxury-oriented trims]
-
A.
offersTrimLevel
chosen
Indicates that a product or model is available in a specific trim level or configuration option.
-
B.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
-
C.
hasNumberOfLevels
Indicates that an entity possesses a specified count of distinct levels or tiers.
-
D.
trimLevel
Indicates the specific configuration or package level of features or options applied to an item, typically distinguishing variants within the same base model.
-
E.
introducedAsTrim
Indicates that an entity is presented or designated as a trim level or variant of another entity (such as a base model).
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2907d0081908291aad66048b8b1 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.