Triple
T28040548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macerata Opera Festival |
E708525
|
entity |
| Predicate | usesLanguageInPerformance |
P43093
|
FINISHED |
| Object | Italian |
—
|
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: Italian | Statement: [Macerata Opera Festival, usesLanguageInPerformance, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLanguageInPerformance Context triple: [Macerata Opera Festival, usesLanguageInPerformance, Italian]
-
A.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
B.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
C.
usesLanguageRuntime
Indicates that an entity operates using, depends on, or is executed within a specific language runtime environment.
-
D.
performedLanguage
chosen
Indicates that an action, work, or performance was carried out using a specified language.
-
E.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 8:25 p.m.