Triple
T31520353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fafner |
E804189
|
entity |
| Predicate | operaCharacterType |
P148812
|
FINISHED |
| Object | bass role |
—
|
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: bass role | Statement: [Fafner, operaCharacterType, bass role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaCharacterType Context triple: [Fafner, operaCharacterType, bass role]
-
A.
operaCharacterName
Indicates that the subject is the name (or names) of a character appearing in an opera.
-
B.
operaCharacterBasedOn
Indicates that an opera character is modeled after, inspired by, or derived from a particular real or fictional person or character.
-
C.
operaOrOratorioCharacterType
chosen
Indicates that the subject is a character type or role as it appears specifically within an opera or an oratorio.
-
D.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
E.
operaTitleCharacter
Indicates that a character is the title (namesake) character of a given opera.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: April 30, 2026, 9:55 p.m.