Triple
T10980253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flentrop organ |
E259483
|
entity |
| Predicate | performancePracticeSupport |
P74486
|
FINISHED |
| Object | articulate Baroque touch |
—
|
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: articulate Baroque touch | Statement: [Flentrop organ, performancePracticeSupport, articulate Baroque touch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performancePracticeSupport Context triple: [Flentrop organ, performancePracticeSupport, articulate Baroque touch]
-
A.
mentionsPractice
Indicates that one entity refers to, discusses, or brings up a particular practice in some form of communication.
-
B.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving another entity.
-
C.
coversPractice
chosen
Indicates that one entity includes, addresses, or provides instruction on a particular practice or set of practices.
-
D.
hasPractices
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
E.
physicalPracticeComponent
Indicates that something is a physical or bodily activity that forms part of a larger practice or routine.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772e97cf88190a65dab3ec4e5f7f3 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.