Triple
T25958949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varsham |
E645483
|
entity |
| Predicate | hasMainProtagonistActor |
P8706
|
FINISHED |
| Object | Prabhas |
—
|
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: Prabhas | Statement: [Varsham, hasMainProtagonistActor, Prabhas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainProtagonistActor Context triple: [Varsham, hasMainProtagonistActor, Prabhas]
-
A.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
-
B.
hasProtagonist
chosen
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
C.
hasHumanProtagonists
Indicates that the primary characters driving the narrative are human beings rather than non-human entities.
-
D.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
E.
laterMainCharacterOf
Indicates that one entity becomes the main character of a work at a later point in time, succeeding another main character.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 22, 2026, 8:47 a.m.