Triple
T30303379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amonasro |
E770708
|
entity |
| Predicate | requiresSingerTraits |
P40358
|
FINISHED |
| Object | strong declamatory style |
—
|
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: strong declamatory style | Statement: [Amonasro, requiresSingerTraits, strong declamatory style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSingerTraits Context triple: [Amonasro, requiresSingerTraits, strong declamatory style]
-
A.
hasHookSinger
Indicates that one entity serves as the hook singer (performing the main recurring vocal refrain) for another entity, typically a song or musical track.
-
B.
singerInstruction
Indicates that one entity provides guidance, direction, or coaching to a singer regarding their singing or performance.
-
C.
isSingerFrom
Indicates that a person is a singer who originates from or is associated with a particular place or region.
-
D.
hasSinging
Indicates that an entity performs, possesses, or is engaged in the action or activity of singing.
-
E.
vocalRequirement
chosen
Indicates that a particular action, role, or participation involves a specified need or condition related to vocal use, such as speaking or singing.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 29, 2026, 7:49 p.m.