Triple
T37124834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Herd |
E919361
|
entity |
| Predicate | associatedInstrumentOfLeader |
P45000
|
FINISHED |
| Object | clarinet |
—
|
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: clarinet | Statement: [First Herd, associatedInstrumentOfLeader, clarinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedInstrumentOfLeader Context triple: [First Herd, associatedInstrumentOfLeader, clarinet]
-
A.
mainInstrumentOfLeader
Indicates that an instrument is the primary or most characteristic instrument used by a particular leader (such as a bandleader or ensemble leader).
-
B.
associatedInstrumentalist
Indicates that an instrumentalist is connected to or involved with another entity, such as a work, performance, or recording, in a relevant musical role.
-
C.
relatedToInstrument
Indicates a general relationship where one entity is connected or associated with a musical instrument.
-
D.
belongsToInstrument
Indicates that something is a component, part, or attribute of a specific instrument.
-
E.
linkedInstrument
chosen
Indicates that one entity is associated with or connected to another as a related or corresponding instrument.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.