Triple
T23822975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erismena |
E589285
|
entity |
| Predicate | hasAriaType |
P16808
|
FINISHED |
| Object | strophic arias |
—
|
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: strophic arias | Statement: [Erismena, hasAriaType, strophic arias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAriaType Context triple: [Erismena, hasAriaType, strophic arias]
-
A.
hasAria
Indicates that one entity possesses, contains, or is associated with an aria (a specific vocal piece or melodic section).
-
B.
hasNotableAriaIn
Indicates that an entity (typically a character or role) has a notable aria featured within a specified musical or operatic work.
-
C.
hasARIAcertification
Indicates that an entity possesses an ARIA (Accessible Rich Internet Applications) certification attesting to compliance with relevant accessibility standards.
-
D.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasEarlyScreenRole
Indicates that an entity played a role in an early stage of another entity’s screen-based career or production history.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7afff6c819096a0af7e008ea8d4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.