Triple
T10126548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rienzi |
E226228
|
entity |
| Predicate | historicalGenreContext |
P52837
|
FINISHED |
| Object | 19th-century grand opera |
—
|
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: 19th-century grand opera | Statement: [Rienzi, historicalGenreContext, 19th-century grand opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalGenreContext Context triple: [Rienzi, historicalGenreContext, 19th-century grand opera]
-
A.
historicalGenre
chosen
Indicates that something belongs to or is categorized within a particular historical genre.
-
B.
historicalContextOfWriting
Indicates that one entity provides the historical circumstances, period, or background in which another entity (typically a text or document) was written.
-
C.
historicallyImportantGenre
Indicates that the subject genre has played a significant and influential role in history or cultural development.
-
D.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
E.
historicalMedium
Indicates that an entity was conveyed, recorded, or expressed through a particular medium or format in its original historical context.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2eef7388190b95ffd02814f2d1f |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.