Triple
T37603387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There's a Fine, Fine Line |
E935583
|
entity |
| Predicate | theatricalCharacterPerformer |
P47022
|
FINISHED |
| Object | Kate Monster |
—
|
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: Kate Monster | Statement: [There's a Fine, Fine Line, theatricalCharacterPerformer, Kate Monster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatricalCharacterPerformer Context triple: [There's a Fine, Fine Line, theatricalCharacterPerformer, Kate Monster]
-
A.
characterPerformer
chosen
Indicates that a performer portrays or voices a particular character in a work.
-
B.
performerCharacterName
Indicates that a performer is associated with or portrays a specific character name in a performance or work.
-
C.
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).
-
D.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
E.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.