Triple
T22828603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakur district |
E565730
|
entity |
| Predicate | dominantSettlementType |
P41867
|
FINISHED |
| Object | villages |
—
|
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: villages | Statement: [Pakur district, dominantSettlementType, villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantSettlementType Context triple: [Pakur district, dominantSettlementType, villages]
-
A.
humanSettlementType
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
B.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
C.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
D.
typicalSettlement
chosen
Indicates that the subject is a common or characteristic type of settlement typically found in the context of the object.
-
E.
historicalSettlementType
Indicates the type or category of settlement an entity was historically classified as (e.g., village, town, city) during a past period.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2a0e308190941064965346f890 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.