Triple
T30371981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidyadhara |
E772572
|
entity |
| Predicate | patronizedRegion |
P13517
|
FINISHED |
| Object | Bundelkhand |
—
|
NE NERFINISHED |
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: Bundelkhand | Statement: [Vidyadhara, patronizedRegion, Bundelkhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronizedRegion Context triple: [Vidyadhara, patronizedRegion, Bundelkhand]
-
A.
patronageArea
chosen
Indicates the geographic or administrative area within which a patron (such as a sponsor, supporter, or benefactor) exercises their support, influence, or protective role.
-
B.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
C.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
D.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
-
E.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6828468708190b2fbd5da2de92b22 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.