Triple
T2190580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson's Baby |
E49850
|
entity |
| Predicate | safetyPositioning |
P37217
|
FINISHED |
| Object | hypoallergenic in marketing |
—
|
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: hypoallergenic in marketing | Statement: [Johnson's Baby, safetyPositioning, hypoallergenic in marketing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyPositioning Context triple: [Johnson's Baby, safetyPositioning, hypoallergenic in marketing]
-
A.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
B.
shieldPosition
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
-
C.
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.
-
D.
safetyEquipment
Indicates that one entity serves as safety equipment used to protect another entity from harm or danger.
-
E.
positionOnGood
Indicates the stance or viewpoint an entity holds regarding a particular good, such as support, opposition, or neutrality.
- 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_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. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:46 p.m.