Triple
T16099466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everyday |
E390576
|
entity |
| Predicate | hasNotablePercussion |
P94754
|
FINISHED |
| Object | handclaps |
—
|
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: handclaps | Statement: [Everyday, hasNotablePercussion, handclaps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePercussion Context triple: [Everyday, hasNotablePercussion, handclaps]
-
A.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
B.
percussion
chosen
Indicates that an entity produces sound by being struck, shaken, or otherwise hit, as in playing or functioning as a percussion instrument.
-
C.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
-
D.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
-
E.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6672848190922b5ebb90e18947 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.