Triple
T27730055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java Monster Loca Moca |
E697406
|
entity |
| Predicate | labelWarning |
P40820
|
FINISHED |
| Object | not recommended for pregnant or nursing women |
—
|
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 recommended for pregnant or nursing women | Statement: [Java Monster Loca Moca, labelWarning, not recommended for pregnant or nursing women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelWarning Context triple: [Java Monster Loca Moca, labelWarning, not recommended for pregnant or nursing women]
-
A.
labelIndication
Indicates that a label or designation is assigned to an entity to specify its indication, purpose, or intended use.
-
B.
warningGivenBy
Indicates that one entity issues or delivers a warning to another entity.
-
C.
warningLabelRequired
Indicates that an item, product, or situation must display a warning label to alert users to potential risks or hazards.
-
D.
warningType
chosen
Indicates the specific category or classification of a warning associated with an entity or event.
-
E.
warningSubject
Indicates that one entity is the topic or focus of a warning issued by another entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:11 p.m.