Triple
T5019169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Hopper |
E112806
|
entity |
| Predicate | hasAddictionHistory |
P37550
|
FINISHED |
| Object | alcohol |
—
|
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: alcohol | Statement: [Jim Hopper, hasAddictionHistory, alcohol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddictionHistory Context triple: [Jim Hopper, hasAddictionHistory, alcohol]
-
A.
hasAddictiveSubstance
Indicates that an entity contains or involves a substance capable of causing addiction in those who use or consume it.
-
B.
hasAddictionPotential
Indicates that one entity (typically a substance or activity) has the capacity to cause another entity (typically a person) to develop dependence or addictive behavior toward it.
-
C.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
D.
hasDrugAddictedProtagonist
Indicates that the work’s main character is portrayed as being addicted to drugs.
-
E.
addiction
Indicates a compulsive dependence of one entity on a substance, activity, or behavior, typically despite negative consequences and difficulty stopping.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7342c62881909acb35849da8761c |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.