Triple
T21132871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scène aux champs |
E520731
|
entity |
| Predicate | hasKeyRoleForInstrument |
P124223
|
FINISHED |
| Object | English horn |
—
|
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: English horn | Statement: [Scène aux champs, hasKeyRoleForInstrument, English horn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyRoleForInstrument Context triple: [Scène aux champs, hasKeyRoleForInstrument, English horn]
-
A.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
-
B.
hasKeyInstrumentalist
chosen
Indicates that an entity (such as a musical work or performance) has a primary or featured instrumental performer associated with it.
-
C.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
D.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another instrument.
-
E.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723574b1481909fe9bebc83f1f3ce |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.