Triple
T34130319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phusro Nagar Parishad |
E875404
|
entity |
| Predicate | governingAreaType |
P92063
|
FINISHED |
| Object | Town |
—
|
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: Town | Statement: [Phusro Nagar Parishad, governingAreaType, Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingAreaType Context triple: [Phusro Nagar Parishad, governingAreaType, Town]
-
A.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
B.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
C.
localGovernmentAreaType
Indicates the specific classification or category of a local government area within an administrative or governmental hierarchy.
-
D.
administrativeTerritoryType
chosen
Indicates the classification of an administrative area according to its level or type of territorial governance (e.g., city, county, province).
-
E.
governsAreaKnownFor
Indicates that a governing entity exercises authority over an area that is notably recognized for a particular characteristic, feature, or attribute.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00d08e8fac8190b59359134e6e1c03 |
completed | May 10, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_6a00d0127c088190a6f5b360450af113 |
completed | May 10, 2026, 6:36 p.m. |
Created at: May 1, 2026, 1:53 a.m.