Triple
T26384450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radamès |
E663237
|
entity |
| Predicate | operaForm |
P192550
|
FINISHED |
| Object | 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: grand opera | Statement: [Radamès, operaForm, grand opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaForm Context triple: [Radamès, operaForm, grand opera]
-
A.
operaComponent
Indicates that one entity is a constituent part or section of an opera associated with the other entity.
-
B.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
C.
operationalForm
Indicates that one entity is the specific operational or executable form of another, more abstract entity.
-
D.
operaEnÁmbito
Indicates that an entity operates, functions, or carries out its activities within a specified domain, field, or scope.
-
E.
appearsInOperaBy
Indicates that one entity (typically a character, role, or element) is featured or takes part in an opera created or composed by another entity.
- F. None of above. chosen
Provenance (4 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_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: April 26, 2026, 11:21 p.m.