Triple
T33133210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruvarur taluk |
E847928
|
entity |
| Predicate | hasPanchayatVillages |
P86422
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tiruvarur taluk, hasPanchayatVillages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanchayatVillages Context triple: [Tiruvarur taluk, hasPanchayatVillages, yes]
-
A.
hasPanchayatSystem
chosen
Indicates that an entity operates under or is governed by a local self-government structure known as the panchayat system.
-
B.
hasVillageCommunity
Indicates that an entity possesses, is associated with, or includes a village-level community as part of its structure or domain.
-
C.
hasPopularVillage
Indicates that an entity is associated with or contains a village that is widely known, well-liked, or frequently visited.
-
D.
hasPrimaryVillages
Indicates that an entity (such as a region or administrative unit) possesses or is associated with one or more main or principal villages.
-
E.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 1:27 a.m.