Triple
T4052637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Gatsby (opera) |
E84617
|
entity |
| Predicate | notableRoleVoiceType |
P46281
|
FINISHED |
| Object | Jay Gatsby – tenor |
—
|
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: Jay Gatsby – tenor | Statement: [The Great Gatsby (opera), notableRoleVoiceType, Jay Gatsby – tenor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRoleVoiceType Context triple: [The Great Gatsby (opera), notableRoleVoiceType, Jay Gatsby – tenor]
-
A.
notableCharacterVoiced
Indicates that a notable character is voiced or performed by a specific voice actor or performer.
-
B.
notableVoiceActor
Indicates that one entity is a voice actor who is especially prominent or well-known for their work on the other entity.
-
C.
hasNotableVocalType
chosen
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
E.
voiceActingRoleIn
Indicates that an entity performs a voice acting role in a specified work or production.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb869c34819097ec3bebe402d37b |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.