Triple
T25693705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemadpanti |
E644261
|
entity |
| Predicate | geographicalConcentration |
P23004
|
FINISHED |
| Object | central India |
—
|
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: central India | Statement: [Hemadpanti, geographicalConcentration, central India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalConcentration Context triple: [Hemadpanti, geographicalConcentration, central India]
-
A.
hasPopulationConcentrationIn
Indicates that a population is densely or significantly clustered within a specified geographic area or region.
-
B.
populationConcentration
chosen
Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
-
C.
largestConcentrationIn
Indicates that something has its highest density, amount, or presence within a specified location or group compared to all other locations or groups.
-
D.
geographicalUsage
Indicates that something is used, applied, or occurs within a particular geographic area or region.
-
E.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 8:32 p.m.