Triple
T29245372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raavanan |
E741425
|
entity |
| Predicate | mainCharacterPlayedBy |
P9616
|
FINISHED |
| Object | Vikram |
—
|
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: Vikram | Statement: [Raavanan, mainCharacterPlayedBy, Vikram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterPlayedBy Context triple: [Raavanan, mainCharacterPlayedBy, Vikram]
-
A.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
B.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
laterMainCharacterOf
Indicates that one entity becomes the main character of a work at a later point in time, succeeding another main character.
-
D.
mainCharacterField
Indicates that one entity is designated as the primary or central character associated with another entity, such as a work or narrative.
-
E.
characterInPlayBy
Indicates that a character appears in or is part of a play authored or created by a specific person.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 12:32 p.m.