Triple
T34332126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajanna Sircilla district |
E881041
|
entity |
| Predicate | hasMandal |
P203501
|
FINISHED |
| Object | Sircilla mandal |
—
|
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: Sircilla mandal | Statement: [Rajanna Sircilla district, hasMandal, Sircilla mandal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMandal Context triple: [Rajanna Sircilla district, hasMandal, Sircilla mandal]
-
A.
hasMandalStatus
Indicates that an entity holds or is assigned a specific mandal-level administrative or organizational status.
-
B.
hasManu
Indicates that an entity is manufactured or produced by a specified manufacturer or producer.
-
C.
hasMandapa
Indicates that a structure (typically a temple) includes or is associated with a mandapa, an attached or nearby pillared hall or pavilion used for rituals or gatherings.
-
D.
hasMast
Indicates that an object possesses or is equipped with a mast as part of its structure.
-
E.
hasMAD
Indicates that an entity possesses or is associated with a specific MAD (e.g., a minimum acceptable distance, mean absolute deviation, or similarly defined MAD-related measure).
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0191d96dc88190ac0823e534f9d704 |
completed | May 11, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_6a01908110448190a46442ffe4d15f5f |
completed | May 11, 2026, 8:17 a.m. |
| PDg | Predicate description generation | batch_6a0191d8cc888190859143c9e459653a |
completed | May 11, 2026, 8:22 a.m. |
Created at: May 1, 2026, 1:58 a.m.