Triple
T25233849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eega |
E632285
|
entity |
| Predicate | leadProtagonistCharacter |
P32529
|
FINISHED |
| Object | Nani as a housefly |
—
|
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: Nani as a housefly | Statement: [Eega, leadProtagonistCharacter, Nani as a housefly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadProtagonistCharacter Context triple: [Eega, leadProtagonistCharacter, Nani as a housefly]
-
A.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
protagonistIs
chosen
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df734648190b24eb3eea5b65dd6 |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:06 p.m.