Triple
T30362398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yennai Arindhaal |
E772322
|
entity |
| Predicate | actorForCharacterHemanika |
P47022
|
FINISHED |
| Object | Trisha Krishnan |
—
|
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: Trisha Krishnan | Statement: [Yennai Arindhaal, actorForCharacterHemanika, Trisha Krishnan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actorForCharacterHemanika Context triple: [Yennai Arindhaal, actorForCharacterHemanika, Trisha Krishnan]
-
A.
performerCharacterName
Indicates that a performer is associated with or portrays a specific character name in a performance or work.
-
B.
mainActorForCharacter_CharlieCrews
Indicates that the referenced person is the primary actor who portrays the character Charlie Crews.
-
C.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
characterPerformer
chosen
Indicates that a performer portrays or voices a particular character in a 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68243b5d8819092d8a0a1261f5fb2 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:58 p.m.