Triple
T7531686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | बरामती |
E178036
|
entity |
| Predicate | लोकसंख्या वर्गीकरण |
P7948
|
FINISHED |
| Object | शहरी |
—
|
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: शहरी | Statement: [बरामती, लोकसंख्या वर्गीकरण, शहरी]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: लोकसंख्या वर्गीकरण Context triple: [बरामती, लोकसंख्या वर्गीकरण, शहरी]
-
A.
populationClass
chosen
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
B.
dividedPopulationOf
Indicates that a population has been split into distinct subgroups or segments, typically based on specified criteria or characteristics.
-
C.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
D.
populationScale
Indicates the relative size or magnitude of a population, typically categorizing it into broad scale levels (e.g., small, medium, large).
-
E.
hatteBevölkerungssystem
Indicates that an entity possessed or was characterized by a particular population system (e.g., a specific way its population was structured, organized, or administered).
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84753fc81908bee2013004ef5fb |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.