Triple
T25235841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oo Antava Oo Oo Antava |
E632333
|
entity |
| Predicate | performedInFilmOpposite |
P160108
|
FINISHED |
| Object | Allu Arjun |
—
|
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: Allu Arjun | Statement: [Oo Antava Oo Oo Antava, performedInFilmOpposite, Allu Arjun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInFilmOpposite Context triple: [Oo Antava Oo Oo Antava, performedInFilmOpposite, Allu Arjun]
-
A.
actúaEn
Indicates that an actor or performer takes part in or appears in a specific production, such as a film, play, or television show.
-
B.
directorSpouseInCast
Indicates that a film’s director is married to someone who appears as a cast member in that same film.
-
C.
partOfFilmographyOf
Indicates that a work (such as a film, show, or role) is included in the body of screen-related works credited to a particular person.
-
D.
associatedWithLeadActorOfFilm
Indicates a relationship where one entity is connected or linked in some relevant way to the lead actor of a specified film.
-
E.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 21, 2026, 1:07 p.m.