Triple
T27939895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenali |
E700712
|
entity |
| Predicate | municipalGrade |
P80007
|
FINISHED |
| Object | selection-grade municipality |
—
|
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: selection-grade municipality | Statement: [Tenali, municipalGrade, selection-grade municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalGrade Context triple: [Tenali, municipalGrade, selection-grade municipality]
-
A.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
B.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
C.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
D.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
E.
hasMunicipalLevel
chosen
Indicates that an entity is associated with a specific level or tier within a municipal (local government) hierarchy.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 7:17 p.m.