Triple
T34345793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Mari people |
E881428
|
entity |
| Predicate | usesTraditionalInstrument |
P8530
|
FINISHED |
| Object | kugikly |
—
|
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: kugikly | Statement: [Hill Mari people, usesTraditionalInstrument, kugikly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTraditionalInstrument Context triple: [Hill Mari people, usesTraditionalInstrument, kugikly]
-
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.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
C.
usesVocalInstrument
Indicates that an entity performs or produces sound using their voice as a musical instrument.
-
D.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
E.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:58 a.m.