Triple
T25455896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge Aspen |
E637912
|
entity |
| Predicate | offeredTrim |
P55815
|
FINISHED |
| Object | base |
—
|
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: base | Statement: [Dodge Aspen, offeredTrim, base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredTrim Context triple: [Dodge Aspen, offeredTrim, base]
-
A.
offersTrimLevel
chosen
Indicates that a product or model is available in a specific trim level or configuration option.
-
B.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
C.
introducedAsTrim
Indicates that an entity is presented or designated as a trim level or variant of another entity (such as a base model).
-
D.
offersMass
Indicates that one entity provides or makes available a certain mass or quantity of material or substance to another entity.
-
E.
offeredBundle
Indicates that one entity has presented a specific combination of items or services together as a bundled offer to another entity.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 21, 2026, 2:04 p.m.