Triple
T10911041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin N-20 |
E257696
|
entity |
| Predicate | associatedInstrumentName |
P45000
|
FINISHED |
| Object | Trigger |
—
|
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: Trigger | Statement: [Martin N-20, associatedInstrumentName, Trigger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedInstrumentName Context triple: [Martin N-20, associatedInstrumentName, Trigger]
-
A.
relatedToInstrument
Indicates a general relationship where one entity is connected or associated with a musical instrument.
-
B.
relatedInstrumentType
Indicates that one instrument is associated with or connected to another by type, such as being a variant, subtype, or closely related form.
-
C.
linkedInstrument
chosen
Indicates that one entity is associated with or connected to another as a related or corresponding instrument.
-
D.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77071492c8190bd6f8623a59464c9 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.