Triple
T33805442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooke Ashton |
E866370
|
entity |
| Predicate | isOnstageRoleOf |
P42172
|
FINISHED |
| Object | Vicki |
—
|
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: Vicki | Statement: [Brooke Ashton, isOnstageRoleOf, Vicki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnstageRoleOf Context triple: [Brooke Ashton, isOnstageRoleOf, Vicki]
-
A.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
B.
portrayedByStageName
Indicates that an entity is depicted or represented by a performer identified specifically by their stage name.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
roleInTheatreEcosystem
Indicates the specific function, responsibility, or position an entity holds within the interconnected system of theatre production, distribution, and audience engagement.
-
E.
playsInRole
chosen
Indicates that an entity performs or appears in a specific role within a production, event, or context.
- 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbe36a08190bf1f2b0529a85f4a |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.