Triple
T27278144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akshara Haasan |
E688250
|
entity |
| Predicate | workedAsAssistantDirectorOn |
P151484
|
FINISHED |
| Object | Society |
—
|
LITERAL FINISHED |
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: Society | Statement: [Akshara Haasan, workedAsAssistantDirectorOn, Society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedAsAssistantDirectorOn Context triple: [Akshara Haasan, workedAsAssistantDirectorOn, Society]
-
A.
wasAssistantDirectorOf
chosen
Indicates that one entity served in the role of assistant director for another entity, such as a film, production, or organization.
-
B.
workedAsDirectorFor
Indicates that one entity held the role of director in relation to another entity, such as an organization, project, or production.
-
C.
workedWithDirector
Indicates that one entity has collaborated professionally with a director on a project or production.
-
D.
workedAsProducerFor
Indicates that one entity served in the role of producer for a work, project, or production associated with another entity.
-
E.
coDirectedWith
Indicates that two or more entities jointly directed the same work or project.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11:04 a.m.