Triple
T35227203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jat-Jatin |
E1017129
|
entity |
| Predicate | artFormFamily |
P182631
|
FINISHED |
| Object | North Indian folk traditions |
—
|
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: North Indian folk traditions | Statement: [Jat-Jatin, artFormFamily, North Indian folk traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artFormFamily Context triple: [Jat-Jatin, artFormFamily, North Indian folk traditions]
-
A.
artForm
Indicates the type or category of artistic expression that characterizes or defines something (e.g., painting, music, dance).
-
B.
textualFamily
Indicates that two or more texts are related through a shared origin, tradition, or lineage, forming a recognizable textual group or family.
-
C.
styleFamily
Indicates that one style is grouped within the same stylistic family or category as another style.
-
D.
patronFamily
Indicates that one family serves as a patron or protector, providing support or sponsorship to another family.
-
E.
artFormIncludes
Indicates that a broader artistic category or practice encompasses or contains a particular art form as one of its components or examples.
- F. None of above. chosen
Provenance (4 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.