Triple
T7574628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fipa |
E179329
|
entity |
| Predicate | traditionalMusicIncludes |
P8530
|
FINISHED |
| Object | drumming |
—
|
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: drumming | Statement: [Fipa, traditionalMusicIncludes, drumming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMusicIncludes Context triple: [Fipa, traditionalMusicIncludes, drumming]
-
A.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
B.
traditionalInstrument
chosen
Indicates that an entity is a musical instrument associated with the traditional or customary music of a particular culture, region, or community.
-
C.
includesTraditionalSong
Indicates that one entity contains or features a traditional song as part of its content or composition.
-
D.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
E.
notableRecordingTradition
Indicates that there exists a significant or historically important tradition of recording or documenting something associated with the subject.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.