Triple
T17311406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diva’s Lament |
E420304
|
entity |
| Predicate | requiresPerformerType |
P116845
|
FINISHED |
| Object | comic belter |
—
|
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: comic belter | Statement: [Diva’s Lament, requiresPerformerType, comic belter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPerformerType Context triple: [Diva’s Lament, requiresPerformerType, comic belter]
-
A.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
C.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
D.
intendedForPerformanceBy
chosen
Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
-
E.
hasPerformerCharacteristic
Indicates that a performer possesses a particular attribute, quality, or characteristic.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439993bac8190a72f6af529bd7cce |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.