Triple
T32512910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buzz Cola |
E830982
|
entity |
| Predicate | healthEffectInFiction |
P19730
|
FINISHED |
| Object | portrayed as unhealthy |
—
|
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: portrayed as unhealthy | Statement: [Buzz Cola, healthEffectInFiction, portrayed as unhealthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthEffectInFiction Context triple: [Buzz Cola, healthEffectInFiction, portrayed as unhealthy]
-
A.
healthEffect
chosen
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
B.
fictionalDisease
Indicates that an entity is associated with, afflicted by, or otherwise characterized by a disease that is imaginary or does not exist in reality.
-
C.
threatenedByInFiction
Indicates that, within a fictional context, one entity is portrayed as being threatened by another entity.
-
D.
worksUnderInFiction
Indicates that, within a fictional context or narrative, one character or entity is hierarchically subordinate to and takes direction from another.
-
E.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1 a.m.