Triple
T20268944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Ground |
E499040
|
entity |
| Predicate | mainArtistInstrument |
P54631
|
FINISHED |
| Object | vibraphone |
—
|
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: vibraphone | Statement: [Common Ground, mainArtistInstrument, vibraphone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainArtistInstrument Context triple: [Common Ground, mainArtistInstrument, vibraphone]
-
A.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
B.
featuresPrimaryInstrument
chosen
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
C.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
D.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
E.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e675dc8e708190b840d687f134c9e8 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:42 p.m.