Triple
T37158074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room 335 |
E920563
|
entity |
| Predicate | associatedInstrumentModel |
P116302
|
FINISHED |
| Object | Gibson ES-335 |
E828819
|
NE 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: Gibson ES-335 | Statement: [Room 335, associatedInstrumentModel, Gibson ES-335]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedInstrumentModel Context triple: [Room 335, associatedInstrumentModel, Gibson ES-335]
-
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.
affectedInstrument
Indicates that an instrument or tool is impacted, altered, or influenced as a result of an action or event.
-
D.
belongsToInstrument
Indicates that something is a component, part, or attribute of a specific instrument.
-
E.
relatesToInstrument
chosen
Indicates a relationship where one entity is associated with, involves, or makes use of a particular instrument or tool.
- F. None of above.
Provenance (4 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40360b7c388190885e2db6a514d1b2 |
completed | June 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.