Triple
T31629312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazue Kato |
E807117
|
entity |
| Predicate | workHasTheme |
P56598
|
FINISHED |
| Object | exorcism |
—
|
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: exorcism | Statement: [Kazue Kato, workHasTheme, exorcism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workHasTheme Context triple: [Kazue Kato, workHasTheme, exorcism]
-
A.
associatedWithWorkTheme
chosen
Indicates a relationship where something is connected or related to a particular work theme or subject matter.
-
B.
hasOccupationTheme
Indicates that something (such as a work or resource) centrally involves or focuses on a particular occupation or type of work as its main theme.
-
C.
hasWorksAbout
Indicates that one entity (such as a creator, collection, or source) includes or is associated with works whose subject or focus is another entity.
-
D.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
E.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8e303148190b0f8959045db3073 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:44 p.m.