Triple
T23172549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Hare of Inaba |
E578895
|
entity |
| Predicate | hasCharacterTraitForHare |
P32341
|
FINISHED |
| Object | cunning |
—
|
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: cunning | Statement: [White Hare of Inaba, hasCharacterTraitForHare, cunning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterTraitForHare Context triple: [White Hare of Inaba, hasCharacterTraitForHare, cunning]
-
A.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
B.
hasTemperament
chosen
Indicates that an entity possesses a particular characteristic style of behavior, mood, or emotional disposition.
-
C.
hasHuntingInstinct
Indicates that an entity possesses an innate tendency or drive to hunt other organisms.
-
D.
hasRacehorseCharacter
Indicates that one entity possesses the traits, qualities, or behavioral characteristics associated with a racehorse in relation to another entity or context.
-
E.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
- 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_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. |
Created at: April 17, 2026, 4:04 p.m.