Triple
T29326010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English horn |
E743643
|
entity |
| Predicate | isNotatedIn |
P133304
|
FINISHED |
| Object | treble clef |
—
|
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: treble clef | Statement: [English horn, isNotatedIn, treble clef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotatedIn Context triple: [English horn, isNotatedIn, treble clef]
-
A.
isNotatedFor
Indicates that something (such as a piece of music or performance) is written or represented in a specific notation system or format.
-
B.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
C.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
D.
appearsInNotation
chosen
Indicates that one entity is represented, referenced, or depicted within the formal notation or symbolic system associated with another entity.
-
E.
notableWorkComposedWith
Indicates that a notable work was created using, in collaboration with, or through the involvement of a particular tool, medium, system, or co-creative entity.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66895a0d481908efba5930e1ec3b9 |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:26 p.m.