Triple
T32723058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cecil Terwilliger |
E836726
|
entity |
| Predicate | wasFiredBy |
P88603
|
FINISHED |
| Object | Krusty the Clown |
—
|
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: Krusty the Clown | Statement: [Cecil Terwilliger, wasFiredBy, Krusty the Clown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFiredBy Context triple: [Cecil Terwilliger, wasFiredBy, Krusty the Clown]
-
A.
firedBy
chosen
Indicates that one entity has dismissed or terminated another entity from a position, role, or employment.
-
B.
firedAt
Indicates that one entity discharged a weapon or projectile in the direction of another entity.
-
C.
firedFrom
Indicates that an entity has been dismissed or terminated from a position, job, or role by another entity.
-
D.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
E.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8b484b48190b5c37ba1c3101056 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.