Triple
T11335194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagar Palika |
E268452
|
entity |
| Predicate | typicalPopulationRange |
P28398
|
FINISHED |
| Object | 20,000 to 100,000 (approximate, varies by state) |
—
|
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: 20,000 to 100,000 (approximate, varies by state) | Statement: [Nagar Palika, typicalPopulationRange, 20,000 to 100,000 (approximate, varies by state)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPopulationRange Context triple: [Nagar Palika, typicalPopulationRange, 20,000 to 100,000 (approximate, varies by state)]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
C.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
D.
populationRange
chosen
Indicates the numerical interval within which the size of a population falls.
-
E.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.