Triple
T24685283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chopi people |
E611266
|
entity |
| Predicate | musicTransmission |
P62259
|
FINISHED |
| Object | oral teaching and apprenticeship |
—
|
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: oral teaching and apprenticeship | Statement: [Chopi people, musicTransmission, oral teaching and apprenticeship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicTransmission Context triple: [Chopi people, musicTransmission, oral teaching and apprenticeship]
-
A.
musicSource
Indicates that one entity serves as the origin or provider of music for another entity or context.
-
B.
musicMotif
Indicates a recurring musical idea, theme, or pattern that appears multiple times within a composition or across related works.
-
C.
musicFocus
Indicates that the primary attention or emphasis is directed toward music or musical aspects.
-
D.
musicActivity
chosen
Indicates involvement in an activity related to creating, performing, practicing, or engaging with music.
-
E.
play
Indicates that an entity engages in a recreational, performative, or competitive activity, often involving a game, sport, or musical performance, typically with another entity or object.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 3:17 a.m.