Triple
T26780174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 九条節子 |
E670224
|
entity |
| Predicate | キャラクター分類 |
P60013
|
FINISHED |
| Object | 怨霊 |
—
|
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: 怨霊 | Statement: [九条節子, キャラクター分類, 怨霊]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: キャラクター分類 Context triple: [九条節子, キャラクター分類, 怨霊]
-
A.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
B.
judgeCharacter
Indicates evaluating or forming an opinion about another entity’s moral qualities, personality, or overall character.
-
C.
classificationAccordingTo
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
D.
characterGenerator
Indicates a relationship where an entity produces, defines, or initializes characters or character data for use in another context.
-
E.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f619795b208190b039e396ab4629b2 |
completed | May 2, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:08 a.m.