Triple
T5293083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alvirah and Willy series |
E119789
|
entity |
| Predicate | mainCharacterStatus |
P46003
|
FINISHED |
| Object | lottery winner |
—
|
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: lottery winner | Statement: [Alvirah and Willy series, mainCharacterStatus, lottery winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterStatus Context triple: [Alvirah and Willy series, mainCharacterStatus, lottery winner]
-
A.
currentCharacter
Indicates that an entity is the character presently in focus or being actively considered in a given context or sequence.
-
B.
leadCharacterStatus
chosen
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
E.
magicalStatus
Indicates that an entity possesses, is affected by, or is characterized in terms of a particular magical condition or property.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.