Triple
T10594796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vemulavada Chalukya |
E250080
|
entity |
| Predicate | patronizedArt |
P43442
|
FINISHED |
| Object | Jain basadis |
—
|
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: Jain basadis | Statement: [Vemulavada Chalukya, patronizedArt, Jain basadis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronizedArt Context triple: [Vemulavada Chalukya, patronizedArt, Jain basadis]
-
A.
publicArt
Indicates that something is an artwork installed or displayed in a publicly accessible space.
-
B.
culturalPatronage
chosen
Indicates the support, promotion, or sponsorship of cultural activities, institutions, or creators by an individual, group, or organization.
-
C.
traditionalPatron
Indicates a relationship where one entity serves as a customary or historically established patron or supporter of another.
-
D.
artSpecialty
Indicates that an entity’s primary focus, expertise, or specialization is in a particular art form or artistic domain.
-
E.
patronageStyle
Indicates the manner or characteristic way in which support, sponsorship, or patronage is provided in a relationship.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278cbf9081909ef419b0144d5019 |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.