Triple
T21204916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanley Jordan |
E522551
|
entity |
| Predicate | playsTechnique |
P70900
|
FINISHED |
| Object | touch technique |
—
|
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: touch technique | Statement: [Stanley Jordan, playsTechnique, touch technique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsTechnique Context triple: [Stanley Jordan, playsTechnique, touch technique]
-
A.
notableInstrumentTechnique
chosen
Indicates that an entity is particularly recognized for using, developing, or being associated with a specific musical instrument technique.
-
B.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
musicalAbility
Indicates that an entity possesses skill, talent, or proficiency in performing, creating, or understanding music.
-
D.
sportsSkill
Indicates that an entity possesses a particular ability, proficiency, or level of competence in performing a sport or sports-related activity.
-
E.
artisticTechnique
Indicates the method, style, or process used to create or execute an artistic work.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734342e9081909e241bed54dbc0b4 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:19 p.m.