Triple
T35289564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agatha Trunchbull |
E1019182
|
entity |
| Predicate | usesPunishment |
P99542
|
FINISHED |
| Object | The Chokey |
—
|
NE NERFINISHED |
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: The Chokey | Statement: [Agatha Trunchbull, usesPunishment, The Chokey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPunishment Context triple: [Agatha Trunchbull, usesPunishment, The Chokey]
-
A.
punishmentIncludes
Indicates that a specified punishment encompasses or contains another specified punitive measure as one of its components.
-
B.
hasPunishment
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
-
C.
punishmentMethod
chosen
Indicates the method or means by which a punishment is carried out on an entity.
-
D.
providesForPunishment
Indicates that one entity establishes or authorizes a penalty or sanction to be imposed on another entity or for a particular action.
-
E.
punishedBy
Indicates that an entity receives punishment administered 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:03 p.m.