Triple
T24257532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet LT |
E603710
|
entity |
| Predicate | comparedToBaseTrim |
P155349
|
FINISHED |
| Object | better equipped |
—
|
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: better equipped | Statement: [Chevrolet LT, comparedToBaseTrim, better equipped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparedToBaseTrim Context triple: [Chevrolet LT, comparedToBaseTrim, better equipped]
-
A.
introducedAsTrim
Indicates that an entity is presented or designated as a trim level or variant of another entity (such as a base model).
-
B.
isTrimOf
Indicates that one entity is a version of another with leading and/or trailing whitespace characters removed.
-
C.
comparedToPredecessor
Indicates that something is being evaluated or measured in relation to the thing that came immediately before it.
-
D.
hasTrimMaterial
Indicates that one entity uses or features a particular material specifically for its trim or edging components.
-
E.
wheelbaseComparedTo
Indicates a comparison between the distances between the front and rear wheel axles (wheelbases) of two entities, specifying how one wheelbase relates in size or length to the other.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6395108190b5310f76e7d78c41 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:05 a.m.