Triple
T32803385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sound Theatre |
E838955
|
entity |
| Predicate | hasMainInstrumentalist |
P124223
|
FINISHED |
| Object | Greg Osby |
—
|
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: Greg Osby | Statement: [Sound Theatre, hasMainInstrumentalist, Greg Osby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainInstrumentalist Context triple: [Sound Theatre, hasMainInstrumentalist, Greg Osby]
-
A.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
B.
hasKeyInstrumentalist
chosen
Indicates that an entity (such as a musical work or performance) has a primary or featured instrumental performer associated with it.
-
C.
hasMajorInstrument
Indicates that an entity’s primary or main musical instrument is a specified instrument.
-
D.
associatedInstrumentalist
Indicates that an instrumentalist is connected to or involved with another entity, such as a work, performance, or recording, in a relevant musical role.
-
E.
hasMainInstrumentalElements
Indicates that one entity includes or is characterized by the primary instrumental components or parts of another entity.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: May 1, 2026, 1:15 a.m.