Triple
T21151653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aricie |
E521205
|
entity |
| Predicate | notableAriaInWork |
P140539
|
FINISHED |
| Object | Temple scenes arias |
—
|
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: Temple scenes arias | Statement: [Aricie, notableAriaInWork, Temple scenes arias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAriaInWork Context triple: [Aricie, notableAriaInWork, Temple scenes arias]
-
A.
notableAria
Indicates that an aria is particularly famous, distinguished, or significant within its artistic or historical context.
-
B.
notableAriaAssociated
chosen
Indicates that a notable aria is associated with, or prominently linked to, a particular entity (such as a person, work, or performance).
-
C.
notableWorkFeaturing
Indicates that a particular notable work (such as a book, film, or artwork) prominently includes, showcases, or is centered around a given entity.
-
D.
notableTheaterWork
Indicates that a theater work is notably associated with, or a significant part of the achievements of, a given entity.
-
E.
notableFromWork
Indicates that an entity is notable or well-known specifically because of a particular work it created, contributed to, or is associated with.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72401830c8190a2008c40c4174d97 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.