Triple
T20213156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanoor |
E493539
|
entity |
| Predicate | localGoverningBody |
P3379
|
FINISHED |
| Object | Gram panchayat |
—
|
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: Gram panchayat | Statement: [Nanoor, localGoverningBody, Gram panchayat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localGoverningBody Context triple: [Nanoor, localGoverningBody, Gram panchayat]
-
A.
hasLocalGovernmentBody
chosen
Indicates that an entity is administered or overseen by a specific local government authority or governing body.
-
B.
governingBodyNearby
Indicates that a governing body is located in close physical proximity to the referenced entity or area.
-
C.
hasLocalAdvisoryBody
Indicates that an entity is supported or overseen by an advisory body that operates at a local or community level.
-
D.
localGovernmentAreaOf
Indicates that one entity is the local government area within whose jurisdiction or administrative boundaries the other entity is located.
-
E.
locationOfGoverningBody
Indicates the place where a governing body is based or carries out its official functions.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed6fe888190b553ba6879cb2d8d |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.