Triple
T3009732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Season of the Witch |
E81986
|
entity |
| Predicate | accusedCharacter |
P21461
|
FINISHED |
| Object | suspected witch |
—
|
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: suspected witch | Statement: [Season of the Witch, accusedCharacter, suspected witch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusedCharacter Context triple: [Season of the Witch, accusedCharacter, suspected witch]
-
A.
questionedCharacter
Indicates that one entity directed questions or an interrogation toward another entity.
-
B.
accusedIn
chosen
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
C.
suspectedPerpetrator
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
-
D.
firstAccused
Indicates that the subject is the primary or earliest individual formally charged or blamed in a particular case or incident.
-
E.
wronglyAccusedBy
Indicates that one entity has falsely or unjustly accused another entity of wrongdoing.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4ccbf08190a7580c9e758804d0 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.