Triple
T29332238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server Sundaram |
E743810
|
entity |
| Predicate | leadActorPerformancePraised |
P163497
|
FINISHED |
| Object | Nagesh |
—
|
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: Nagesh | Statement: [Server Sundaram, leadActorPerformancePraised, Nagesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorPerformancePraised Context triple: [Server Sundaram, leadActorPerformancePraised, Nagesh]
-
A.
leadActorPerformanceDescribedAs
chosen
Indicates that the performance of the lead actor in a work is characterized or described using a particular quality, opinion, or assessment.
-
B.
leadActorAwarded
Indicates that the person in the lead actor role has received an award for their performance.
-
C.
leadActorNominee
Indicates that an entity was nominated for a lead acting role in relation to a particular work or award.
-
D.
leadActorOfWinningFilm
Indicates that a person is the lead actor in a film that has won a specified award or competition.
-
E.
notablePrimaryPerformance
Indicates that an entity is recognized for a primary or leading performance in a work or event.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 1:30 p.m.