Triple
T312459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubians |
E7635
|
entity |
| Predicate | traditionalMusicInstruments |
P8530
|
FINISHED |
| Object | tambour (frame drum) |
—
|
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: tambour (frame drum) | Statement: [Nubians, traditionalMusicInstruments, tambour (frame drum)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMusicInstruments Context triple: [Nubians, traditionalMusicInstruments, tambour (frame drum)]
-
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.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
C.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
D.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
E.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.