Triple
T11336271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manganiyar folk music |
E268478
|
entity |
| Predicate | patronageTradition |
P40860
|
FINISHED |
| Object | hereditary patron-client system |
—
|
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: hereditary patron-client system | Statement: [Manganiyar folk music, patronageTradition, hereditary patron-client system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronageTradition Context triple: [Manganiyar folk music, patronageTradition, hereditary patron-client system]
-
A.
patronage
Indicates a relationship where one party supports, sponsors, or protects another, often in exchange for loyalty, services, or influence.
-
B.
patronageStyle
chosen
Indicates the manner or characteristic way in which support, sponsorship, or patronage is provided in a relationship.
-
C.
patronageFocus
Indicates the primary area, subject, or domain that is the focus of an entity’s support, sponsorship, or patronage.
-
D.
patronageFrom
Indicates a relationship where support, sponsorship, or backing is provided to someone or something by a patron.
-
E.
traditionalPatron
Indicates a relationship where one entity serves as a customary or historically established patron or supporter of another.
- 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.