Triple
T26606125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Newgrass |
E667776
|
entity |
| Predicate | hasNotableInstrumentContext |
P193990
|
FINISHED |
| Object | mandolin |
—
|
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: mandolin | Statement: [King of Newgrass, hasNotableInstrumentContext, mandolin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableInstrumentContext Context triple: [King of Newgrass, hasNotableInstrumentContext, mandolin]
-
A.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
-
B.
hasInstrumentClass
Indicates that an action or process is carried out using an instrument that belongs to a specified class or category of instruments.
-
C.
hasNotableGenreContext
Indicates that an entity’s genre is significant or noteworthy in understanding its context, interpretation, or impact.
-
D.
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.
-
E.
hasMajorInstrument
chosen
Indicates that an entity’s primary or main musical instrument is a specified 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 27, 2026, 2:14 a.m.