Triple
T29634657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vedalam |
E755677
|
entity |
| Predicate | leadActorPreviousCollaborationWithDirector |
P177154
|
FINISHED |
| Object | Veeram |
—
|
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: Veeram | Statement: [Vedalam, leadActorPreviousCollaborationWithDirector, Veeram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorPreviousCollaborationWithDirector Context triple: [Vedalam, leadActorPreviousCollaborationWithDirector, Veeram]
-
A.
precededByCollaborationWithDirector
Indicates that an event or work occurred after, and was directly preceded by, a collaboration with a specified director.
-
B.
filmDirectorWorkedWith
Indicates that a film director has collaborated professionally with another person on one or more film projects.
-
C.
leadActorAlsoDirector
Indicates that the person who plays the lead acting role in a production is also the director of that same production.
-
D.
associatedWithDirectors
Indicates a direct relationship or connection between an entity and one or more film or project directors.
-
E.
hasDirectorStar
Indicates that a person both directed and starred in the same work (e.g., film, show, or production).
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 6:43 p.m.