Triple
T19428955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lankapati |
E486058
|
entity |
| Predicate | usedForCharacterType |
P135851
|
FINISHED |
| Object | demon-king |
—
|
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: demon-king | Statement: [Lankapati, usedForCharacterType, demon-king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForCharacterType Context triple: [Lankapati, usedForCharacterType, demon-king]
-
A.
helpsCharacterType
Indicates that one character type provides assistance or support to another character type.
-
B.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
C.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
-
D.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
E.
workCharacterType
Indicates that a work involves or features a character of a specified type or role.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6321b78d08190b86cef7c60cbb61c |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.