Triple
T32742123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection |
E837243
|
entity |
| Predicate | associatedWithInstrumentation |
P142440
|
FINISHED |
| Object | large orchestra |
—
|
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: large orchestra | Statement: [Resurrection, associatedWithInstrumentation, large orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithInstrumentation Context triple: [Resurrection, associatedWithInstrumentation, large orchestra]
-
A.
hasInstrumentationProvidedBy
Indicates that the instrumentation used in an activity, process, or work is supplied or made available by a specified provider.
-
B.
belongsToInstrument
Indicates that something is a component, part, or attribute of a specific instrument.
-
C.
usedInstrumentation
chosen
Indicates that an action or process was carried out using a particular instrument or tool as its means or method.
-
D.
relatedToInstrument
Indicates a general relationship where one entity is connected or associated with a musical instrument.
-
E.
backingInstrumentation
Indicates that one musical part, track, or performer provides instrumental accompaniment or background support for another.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:12 a.m.