Triple
T30383120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabukimonogatari |
E772879
|
entity |
| Predicate | franchiseMainCharacter |
P52434
|
FINISHED |
| Object | Koyomi Araragi |
—
|
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: Koyomi Araragi | Statement: [Kabukimonogatari, franchiseMainCharacter, Koyomi Araragi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseMainCharacter Context triple: [Kabukimonogatari, franchiseMainCharacter, Koyomi Araragi]
-
A.
franchiseCharacter
chosen
Indicates a relationship where a character belongs to, appears in, or is part of a particular media franchise.
-
B.
franchiseOriginCharacter
Indicates that a character is the original or primary character from which a franchise or its derivative works originate.
-
C.
hasFranchiseProtagonistTrait
Indicates that a protagonist in a franchise possesses a specific recurring trait or characteristic associated with that franchise.
-
D.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
-
E.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:01 p.m.