Triple
T22506178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giulio Cesare in Egitto |
E556393
|
entity |
| Predicate | modernCaesarVoiceType |
P2000
|
FINISHED |
| Object | countertenor |
—
|
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: countertenor | Statement: [Giulio Cesare in Egitto, modernCaesarVoiceType, countertenor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCaesarVoiceType Context triple: [Giulio Cesare in Egitto, modernCaesarVoiceType, countertenor]
-
A.
voiceTexture
Indicates the characteristic quality or timbre of a voice as perceived in sound.
-
B.
coCaesarWith
Indicates that two individuals simultaneously held the title or role of Caesar together, sharing imperial authority during the same period.
-
C.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
D.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
E.
governedAsCaesar
Indicates that an entity exercised ruling authority in the capacity or role of a Caesar (emperor).
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5cddf88190821d9c9fdee84160 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.