Triple
T21714653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrie (Mozart Requiem) |
E535993
|
entity |
| Predicate | usesOrchestraSection |
P51473
|
FINISHED |
| Object | strings |
—
|
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: strings | Statement: [Kyrie (Mozart Requiem), usesOrchestraSection, strings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOrchestraSection Context triple: [Kyrie (Mozart Requiem), usesOrchestraSection, strings]
-
A.
hasOrchestraSection
chosen
Indicates that something includes or is associated with a particular section of an orchestra.
-
B.
usesOrchestrationSimilarTo
Indicates that one entity employs an orchestration approach or mechanism that is similar to that used by another entity.
-
C.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
D.
orchestrationIncludes
Indicates that one orchestration contains, incorporates, or makes use of another orchestration as part of its overall structure or process.
-
E.
hasSymphonyOrchestra
Indicates that an entity possesses, hosts, or is associated with a symphony orchestra.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5369be88190bafc10863d4d1bd7 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.