Triple
T31045199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosrite guitar |
E791104
|
entity |
| Predicate | usedByMusician |
P46218
|
FINISHED |
| Object | Johnny Ramone |
—
|
NE NERFINISHED |
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: Johnny Ramone | Statement: [Mosrite guitar, usedByMusician, Johnny Ramone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByMusician Context triple: [Mosrite guitar, usedByMusician, Johnny Ramone]
-
A.
employedMusician
Indicates that a musician is employed, typically by an organization, venue, or individual, to perform musical work.
-
B.
usesMusicFor
Indicates that one entity employs or applies music as a means, tool, or resource to achieve or support some purpose, activity, or effect for another entity or context.
-
C.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
D.
usedByArtist
chosen
Indicates that something (such as a tool, material, or method) is employed or utilized by an artist in their work or practice.
-
E.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 8:59 p.m.