Triple
T26976808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khond |
E679479
|
entity |
| Predicate | notableDistrictConcentration |
P199851
|
FINISHED |
| Object | Kandhamal district |
—
|
NE NERFINISHED |
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: Kandhamal district | Statement: [Khond, notableDistrictConcentration, Kandhamal district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDistrictConcentration Context triple: [Khond, notableDistrictConcentration, Kandhamal district]
-
A.
notableDistrictCovered
Indicates that a place or entity includes within its area a district that is considered notable or significant.
-
B.
notableStateConcentration
Indicates that a significant portion of the instances or activity of something is concentrated within a particular state or region.
-
C.
hasPopulationConcentrationIn
Indicates that a population is densely or significantly clustered within a specified geographic area or region.
-
D.
typicalDistricts
Indicates that certain districts are characteristic or representative examples of a larger region, category, or entity.
-
E.
notableUrbanEnclave
Indicates that an entity is recognized as a distinct, significant urban area or neighborhood within a larger city or metropolitan region.
- F. None of above. chosen
Provenance (4 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69ff5f5ddfcc819092563419f9e82d60 |
completed | May 9, 2026, 4:22 p.m. |
Created at: April 27, 2026, 6:43 a.m.