Triple
T37381434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Oratorio |
E928440
|
entity |
| Predicate | hasInstrumentalIntroduction |
P140038
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Easter Oratorio, hasInstrumentalIntroduction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentalIntroduction Context triple: [Easter Oratorio, hasInstrumentalIntroduction, yes]
-
A.
containsInstrumentalTrack
chosen
Indicates that one entity includes or features an instrumental music track as part of its content.
-
B.
hasInstrumentalOrigin
Indicates that something originates from, or is derived through, the use of a particular instrument or means.
-
C.
hasMainInstrumentalElements
Indicates that one entity includes or is characterized by the primary instrumental components or parts of another entity.
-
D.
hasPianoIntroBy
Indicates that something (typically a musical work) features an introductory section played on piano that is performed or created by a specified agent.
-
E.
hasInstrumentalPerformer
Indicates that an action, event, or work is performed or carried out by an entity serving as its instrumental performer.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0116ca6a1c81909a9e938dbe54eb8a |
completed | May 10, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_6a0116655e248190bdfe5b4bb4f1cf47 |
completed | May 10, 2026, 11:36 p.m. |
Created at: May 3, 2026, 4:16 p.m.