Triple
T2190489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Listerine |
E49848
|
entity |
| Predicate | safetyWarning |
P32294
|
FINISHED |
| Object | not to be swallowed |
—
|
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: not to be swallowed | Statement: [Listerine, safetyWarning, not to be swallowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyWarning Context triple: [Listerine, safetyWarning, not to be swallowed]
-
A.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
B.
notableSafety
Indicates that an entity is recognized for having significant safety characteristics, performance, or impact relative to others.
-
C.
safetyRelevant
Indicates that the associated entity, condition, or information has a direct impact on safety or is critical for preventing harm or accidents.
-
D.
safetyRequirement
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
-
E.
safetyLabel
chosen
Indicates that an entity has been assigned a safety-related classification or warning status.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.