Triple
T12883825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally |
E308169
|
entity |
| Predicate | portrayedInStageBy |
P9616
|
FINISHED |
| Object | various stage 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 stage actresses | Statement: [Sally, portrayedInStageBy, various stage actresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedInStageBy Context triple: [Sally, portrayedInStageBy, various stage actresses]
-
A.
stagePortrayalIncludes
Indicates that a stage portrayal incorporates or features a particular element, character, action, or aspect within the performance.
-
B.
portrayedInBroadwayProductionBy
Indicates that an entity was depicted or performed in a Broadway stage production by a specified person or group.
-
C.
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.
-
D.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
E.
playedBy
chosen
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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.