Triple
T25344021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GT Plus |
E635494
|
entity |
| Predicate | addsOverBaseTrim |
P150602
|
FINISHED |
| Object | additional technology 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: additional technology features | Statement: [GT Plus, addsOverBaseTrim, additional technology features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsOverBaseTrim Context triple: [GT Plus, addsOverBaseTrim, additional technology features]
-
A.
addsOverBase
chosen
Indicates that something is added on top of an existing base amount, value, or structure.
-
B.
introducedAsTrim
Indicates that an entity is presented or designated as a trim level or variant of another entity (such as a base model).
-
C.
customizableFeatures
Indicates that certain aspects or options of an entity can be modified or configured according to specific preferences or requirements.
-
D.
aftermarketSupport
Indicates that one entity provides maintenance, service, or assistance for another entity after the initial sale or deployment.
-
E.
hasColumbiaNameOnTrim
Indicates that an object features the Columbia brand name printed or displayed on its trim.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498ba4384819094bb42f61fac6bf6 |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:32 p.m.