Triple
T6279605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shug Avery |
E140746
|
entity |
| Predicate | portrayedInStageMusicalBy |
P9616
|
FINISHED |
| Object | various actresses |
—
|
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: various actresses | Statement: [Shug Avery, portrayedInStageMusicalBy, various actresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedInStageMusicalBy Context triple: [Shug Avery, portrayedInStageMusicalBy, various actresses]
-
A.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
B.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
originalBroadwayStar
Indicates that the subject was a member of the original Broadway cast in the specified role or production.
-
D.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
E.
notableBroadwayPerformer
Indicates that the subject is a performer who has achieved notable recognition for work on Broadway productions.
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063dc55d48190b5ed48a50f3a742e |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.