Triple
T26530203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongolian Dance |
E670799
|
entity |
| Predicate | usesMelodiesFrom |
P37245
|
FINISHED |
| Object | Mongolian folk music |
—
|
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: Mongolian folk music | Statement: [Mongolian Dance, usesMelodiesFrom, Mongolian folk music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMelodiesFrom Context triple: [Mongolian Dance, usesMelodiesFrom, Mongolian folk music]
-
A.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
B.
melodyReusedBy
chosen
Indicates that a melody originally used in one work is later reused or incorporated in another work.
-
C.
hasMultipleMelodies
Indicates that an entity is associated with more than one distinct melody.
-
D.
hasMelodyInstrument
Indicates that something uses or features a particular instrument to carry the main melody.
-
E.
usesInstrumentalsFrom
Indicates that one entity incorporates or makes use of the instrumental tracks or instrumental components created or provided by another entity.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 1:35 a.m.