Triple
T34954461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNU All-permissive License |
E1008090
|
entity |
| Predicate | requiresWarrantyDisclaimer |
P200349
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [GNU All-permissive License, requiresWarrantyDisclaimer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresWarrantyDisclaimer Context triple: [GNU All-permissive License, requiresWarrantyDisclaimer, true]
-
A.
hasWarrantyDisclaimer
Indicates that a product, service, or agreement includes a statement limiting or denying warranties or liability.
-
B.
warrantyClause
Indicates that a contractual provision defines the scope, conditions, and duration of a warranty obligation between parties.
-
C.
haveWarranty
Indicates that one entity provides or is covered by a warranty in relation to another entity.
-
D.
warrantyType
Indicates the specific category or kind of warranty associated with a product, service, or agreement.
-
E.
hasLiabilityDisclaimer
Indicates that an entity includes or is associated with a statement limiting or excluding legal responsibility for certain actions, outcomes, or information.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4 p.m.