Triple
T10263397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camel Turkish Gold |
E240654
|
entity |
| Predicate | warningLabelRequirement |
P78373
|
FINISHED |
| Object | health warnings on packaging |
—
|
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: health warnings on packaging | Statement: [Camel Turkish Gold, warningLabelRequirement, health warnings on packaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningLabelRequirement Context triple: [Camel Turkish Gold, warningLabelRequirement, health warnings on packaging]
-
A.
warningLabelRequired
chosen
Indicates that an item, product, or situation must display a warning label to alert users to potential risks or hazards.
-
B.
warningSubject
Indicates that one entity is the topic or focus of a warning issued by another entity.
-
C.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
D.
warningGivenBy
Indicates that one entity issues or delivers a warning to another entity.
-
E.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2872830819080fdfa816167d04c |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:33 a.m.