Triple
T11336272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manganiyar folk music |
E268478
|
entity |
| Predicate | traditionalPatrons |
P44199
|
FINISHED |
| Object | Rajput Hindu families |
—
|
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: Rajput Hindu families | Statement: [Manganiyar folk music, traditionalPatrons, Rajput Hindu families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPatrons Context triple: [Manganiyar folk music, traditionalPatrons, Rajput Hindu families]
-
A.
traditionalPatron
chosen
Indicates a relationship where one entity serves as a customary or historically established patron or supporter of another.
-
B.
laterPatron
Indicates that one entity serves as a patron of another at a later time than some reference patronage relationship.
-
C.
primaryPatron
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
D.
patronType
Indicates the classification or category of a patron in relation to a service, institution, or resource.
-
E.
historicalPatron
Indicates that one entity served as a patron or sponsor of another in a historical context, providing support, protection, or resources.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.