Triple
T25296098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banjara community |
E634221
|
entity |
| Predicate | traditionalJewellery |
P75226
|
FINISHED |
| Object | heavy silver ornaments |
—
|
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: heavy silver ornaments | Statement: [Banjara community, traditionalJewellery, heavy silver ornaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalJewellery Context triple: [Banjara community, traditionalJewellery, heavy silver ornaments]
-
A.
typicalJewellery
chosen
Indicates that the object is a kind of jewellery that is commonly or characteristically associated with the given entity.
-
B.
typeOfJewellery
Indicates the specific kind or category of jewellery that an item belongs to.
-
C.
traditionalTrade
Indicates a relationship where goods or services are exchanged using long-established, customary methods rather than modern or digital trading systems.
-
D.
earrings
Indicates that one entity is wearing, adorned with, or characterized by earrings.
-
E.
traditionalCraft
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 1:22 p.m.