Triple
T26384470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radamès |
E663237
|
entity |
| Predicate | actOfFamousAria |
P140539
|
FINISHED |
| Object | Act I |
—
|
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: Act I | Statement: [Radamès, actOfFamousAria, Act I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actOfFamousAria Context triple: [Radamès, actOfFamousAria, Act I]
-
A.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
B.
notableAria
Indicates that an aria is particularly famous, distinguished, or significant within its artistic or historical context.
-
C.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
D.
notableStar
Indicates that the subject is a star (or stellar object) that is distinguished or noteworthy in some significant way, such as brightness, fame, or scientific interest, relative to other stars.
-
E.
notableAriaAssociated
chosen
Indicates that a notable aria is associated with, or prominently linked to, a particular entity (such as a person, work, or performance).
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610784f7481908cc17baeac8a23e4 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:21 p.m.