Triple
T27075186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 15 Park Avenue |
E685440
|
entity |
| Predicate | actorForCharacter_Anjali |
P94795
|
FINISHED |
| Object | Shabana Azmi |
—
|
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: Shabana Azmi | Statement: [15 Park Avenue, actorForCharacter_Anjali, Shabana Azmi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actorForCharacter_Anjali Context triple: [15 Park Avenue, actorForCharacter_Anjali, Shabana Azmi]
-
A.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
B.
performerCharacterName
chosen
Indicates that a performer is associated with or portrays a specific character name in a performance or work.
-
C.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
D.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
-
E.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623159a7c819089028373790db00f |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:30 a.m.