Triple
T35244596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln SUVs |
E1017622
|
entity |
| Predicate | hasWarrantyType |
P22687
|
FINISHED |
| Object | limited new-vehicle warranty |
—
|
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: limited new-vehicle warranty | Statement: [Lincoln SUVs, hasWarrantyType, limited new-vehicle warranty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarrantyType Context triple: [Lincoln SUVs, hasWarrantyType, limited new-vehicle warranty]
-
A.
haveWarranty
Indicates that one entity provides or is covered by a warranty in relation to another entity.
-
B.
warrantyType
chosen
Indicates the specific category or kind of warranty associated with a product, service, or agreement.
-
C.
hasWarrantyDisclaimer
Indicates that a product, service, or agreement includes a statement limiting or denying warranties or liability.
-
D.
typeOfGuarantees
Indicates the specific kind or category of guarantees that one entity provides, holds, or is associated with in relation to another.
-
E.
warrantyClause
Indicates that a contractual provision defines the scope, conditions, and duration of a warranty obligation between parties.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:02 p.m.