Triple
T26696898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watch What Happens |
E673046
|
entity |
| Predicate | performerInStageVersion |
P146210
|
FINISHED |
| Object | Kara Lindsay |
—
|
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: Kara Lindsay | Statement: [Watch What Happens, performerInStageVersion, Kara Lindsay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerInStageVersion Context triple: [Watch What Happens, performerInStageVersion, Kara Lindsay]
-
A.
portrayedByStageName
Indicates that an entity is depicted or represented by a performer identified specifically by their stage name.
-
B.
performerInShow
chosen
Indicates that an entity participates as a performer in a particular show or performance.
-
C.
performedOnStageWith
Indicates that two or more entities appeared and performed together in the same stage event or production.
-
D.
performedOnStage
Indicates that a performance, act, or presentation took place in front of an audience on a stage.
-
E.
revivalVersionPerformer
Indicates that an entity performs or is responsible for a revival version of another entity (such as a work, production, or performance).
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 3:29 a.m.