Triple
T23172551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Hare of Inaba |
E578895
|
entity |
| Predicate | hasCharacterTraitForŌkuninushi |
P151210
|
FINISHED |
| Object | compassionate |
—
|
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: compassionate | Statement: [White Hare of Inaba, hasCharacterTraitForŌkuninushi, compassionate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterTraitForŌkuninushi Context triple: [White Hare of Inaba, hasCharacterTraitForŌkuninushi, compassionate]
-
A.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
B.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
C.
hasTitleCharacterTrait
Indicates that a title is associated with a specific character trait of an entity.
-
D.
hasNotableTraitInPlot
Indicates that a character or entity possesses a distinctive trait that plays a significant role within the narrative or plot.
-
E.
hasOmamori
Indicates that one entity possesses or is associated with an omamori (a protective charm or amulet).
- F. None of above. chosen
Provenance (4 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f30ce148190a6de928c8213399e |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:04 p.m.