Triple
T9430688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ČW 26 |
E227365
|
entity |
| Predicate | workInstrumentation |
P29323
|
FINISHED |
| Object | symphony 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: symphony orchestra | Statement: [ČW 26, workInstrumentation, symphony orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInstrumentation Context triple: [ČW 26, workInstrumentation, symphony orchestra]
-
A.
typicalInstrumentation
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
B.
coInstrumentWith
Indicates that two or more entities are used together as instruments or means to perform the same action or achieve the same outcome.
-
C.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
D.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
-
E.
originalInstrumentation
chosen
Indicates the relationship between a musical work and the specific instruments or ensemble for which it was initially scored or conceived.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.