Triple
T7424335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadway production of "Aida" |
E171329
|
entity |
| Predicate | rolePortrayed |
P54972
|
FINISHED |
| Object | Heather Headley as Aida |
—
|
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: Heather Headley as Aida | Statement: [Broadway production of "Aida", rolePortrayed, Heather Headley as Aida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rolePortrayed Context triple: [Broadway production of "Aida", rolePortrayed, Heather Headley as Aida]
-
A.
characterPortrayedIs
chosen
Indicates that one entity serves as the fictional or dramatic role that is depicted or played by another entity.
-
B.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
C.
wasPortrayedAs
Indicates that one entity has been depicted or represented in the form or role of another entity, typically within some medium or context.
-
D.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
roleCharacteristic
Indicates that a particular characteristic, quality, or attribute is associated with and helps define a given role or function.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f302b33481908eae877970f2bbdf |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.