Triple
T29492516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polladhavan |
E748117
|
entity |
| Predicate | mainActorForCharacterPrabhu |
P172157
|
FINISHED |
| Object | Dhanush |
—
|
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: Dhanush | Statement: [Polladhavan, mainActorForCharacterPrabhu, Dhanush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainActorForCharacterPrabhu Context triple: [Polladhavan, mainActorForCharacterPrabhu, Dhanush]
-
A.
actorForCharacterThenmozhi
Indicates that an entity serves as the actor portraying the character Thenmozhi.
-
B.
mainActorForCharacter_CharlieCrews
Indicates that the referenced person is the primary actor who portrays the character Charlie Crews.
-
C.
primaryActor
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
-
D.
characterInFocus
Indicates that a particular character is the primary subject or focal point within a given context, scene, or narrative segment.
-
E.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
- F. None of above. chosen
Provenance (4 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 4:15 p.m.