Triple
T16601523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forro people |
E403340
|
entity |
| Predicate | traditionalMusicInstrumentUse |
P8530
|
FINISHED |
| Object | percussion instruments |
—
|
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: percussion instruments | Statement: [Forro people, traditionalMusicInstrumentUse, percussion instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMusicInstrumentUse Context triple: [Forro people, traditionalMusicInstrumentUse, percussion instruments]
-
A.
traditionalInstrument
chosen
Indicates that an entity is a musical instrument associated with the traditional or customary music of a particular culture, region, or community.
-
B.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
C.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
usesMusicEnsemble
Indicates that one entity employs or incorporates a particular music ensemble in carrying out an action, function, or production.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d764574819081366374ca0c9bea |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.