Triple
T6006394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcina |
E133719
|
entity |
| Predicate | hasRecitativeType |
P62940
|
FINISHED |
| Object | secco recitative |
—
|
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: secco recitative | Statement: [Alcina, hasRecitativeType, secco recitative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecitativeType Context triple: [Alcina, hasRecitativeType, secco recitative]
-
A.
hasProsodicType
chosen
Indicates that one entity is characterized by a particular prosodic pattern or category (such as stress, intonation, or rhythm type) in relation to another.
-
B.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
hasLyricalRegister
Indicates that something (such as a text, utterance, or expression) is associated with a particular lyrical or stylistic register in language.
-
E.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f128354819088971ee398cbda77 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.