Triple
T31747704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taps |
E810316
|
entity |
| Predicate | hasNumberOfNotes |
P195731
|
FINISHED |
| Object | 24 |
—
|
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: 24 | Statement: [Taps, hasNumberOfNotes, 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfNotes Context triple: [Taps, hasNumberOfNotes, 24]
-
A.
typeOfNotes
Indicates the specific category or kind of notes associated with an entity or context.
-
B.
hasPitchCount
Indicates that an entity is associated with a specific number of pitches, representing how many pitches have occurred or been recorded for it.
-
C.
hasNumberOfCards
Indicates that an entity is associated with a specific quantity of cards.
-
D.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
E.
hasBaseNote
Indicates that one entity serves as the fundamental or underlying note upon which another entity (such as a chord, scale, or musical structure) is built.
- F. None of above. chosen
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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: April 30, 2026, 11:27 p.m.