Triple
T3253161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordo Nahum |
E68231
|
entity |
| Predicate | isCharacterType |
P10724
|
FINISHED |
| Object | supporting character |
—
|
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: supporting character | Statement: [Mordo Nahum, isCharacterType, supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharacterType Context triple: [Mordo Nahum, isCharacterType, supporting character]
-
A.
hasTypicalCharacterType
chosen
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
B.
characterSetType
Indicates the type or category of character set associated with or used by an entity.
-
C.
judgeCharacter
Indicates evaluating or forming an opinion about another entity’s moral qualities, personality, or overall character.
-
D.
textCharacter
Indicates that one entity is a character (such as a letter, digit, or symbol) within a piece of text associated with another entity.
-
E.
legalCharacter
Indicates that an entity possesses a status, role, or nature that is recognized and defined by law.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf640fd8819083c3c0cc41db2ffc |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.