Triple
T22580368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abra |
E544549
|
entity |
| Predicate | operaOrOratorioCharacterType |
P148812
|
FINISHED |
| Object | servant |
—
|
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: servant | Statement: [Abra, operaOrOratorioCharacterType, servant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaOrOratorioCharacterType Context triple: [Abra, operaOrOratorioCharacterType, servant]
-
A.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
B.
operaTitleCharacter
Indicates that a character is the title (namesake) character of a given opera.
-
C.
associatedOpera
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
-
D.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
E.
inOperaRepertoire
Indicates that a musical work is included as part of the standard or active repertoire performed in opera productions.
- F. None of above. chosen
Provenance (4 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15ff065308190bca9fb24b47757e6 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:53 p.m.