Triple
T26809251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brick Pollitt |
E671937
|
entity |
| Predicate | causeOfAlcoholism |
P125612
|
FINISHED |
| Object | guilt over Skipper's death |
—
|
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: guilt over Skipper's death | Statement: [Brick Pollitt, causeOfAlcoholism, guilt over Skipper's death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfAlcoholism Context triple: [Brick Pollitt, causeOfAlcoholism, guilt over Skipper's death]
-
A.
alcohol
Indicates that one entity is an alcoholic beverage or contains alcohol in relation to another entity.
-
B.
reasonForAddiction
chosen
Indicates the causal factor or circumstance that leads an entity to become addicted.
-
C.
alcoholicCategory
Indicates that one entity is classified as a type or category within the domain of alcoholic beverages in relation to another entity.
-
D.
drinkingHabit
Indicates an entity’s typical pattern or frequency of consuming alcoholic or other beverages.
-
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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 4:28 a.m.