Triple
T11984791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Teavee |
E285249
|
entity |
| Predicate | vice |
P102734
|
FINISHED |
| Object | excessive television watching |
—
|
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: excessive television watching | Statement: [Mike Teavee, vice, excessive television watching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vice Context triple: [Mike Teavee, vice, excessive television watching]
-
A.
vise
Indicates that one entity firmly grips, clamps, or holds another in place, typically restricting its movement or separating it from other objects.
-
B.
via
Indicates that something occurs, is achieved, or is connected by means of, through the use of, or along the route of another entity or medium.
-
C.
verse
Indicates that one entity is in opposition or conflict against another, as in a competitive or adversarial relationship.
-
D.
vicePresident
Indicates that one entity holds the role of second-in-command or deputy leader to another entity within an organizational or governmental hierarchy.
-
E.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.