Triple
T35871160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabia (in some translations) |
E1037226
|
entity |
| Predicate | refersToProtagonist |
P60518
|
FINISHED |
| Object | Rabia |
—
|
NE NERFINISHED |
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: Rabia | Statement: [Rabia (in some translations), refersToProtagonist, Rabia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToProtagonist Context triple: [Rabia (in some translations), refersToProtagonist, Rabia]
-
A.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
B.
refersToCharacter
chosen
Indicates that one entity makes reference to, mentions, or points to a specific character as its subject.
-
C.
representsForProtagonist
Indicates that one entity serves as a representative or stand-in on behalf of the protagonist in some context or interaction.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 3, 2026, 4:06 p.m.