Triple
T25684940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Census of India |
E644040
|
entity |
| Predicate | ruralPopulationShare |
P75008
|
FINISHED |
| Object | 68.84 percent |
—
|
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: 68.84 percent | Statement: [2011 Census of India, ruralPopulationShare, 68.84 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruralPopulationShare Context triple: [2011 Census of India, ruralPopulationShare, 68.84 percent]
-
A.
hasRuralAreaShare
chosen
Indicates the proportion of an entity’s total area or population that is classified as rural.
-
B.
isPredominantlyRural
Indicates that a place or region is characterized mainly by rural features, such as low population density and extensive non-urban land use.
-
C.
populationShareApproximate
Indicates that one entity’s share of a total population is approximately equal to a specified proportion or percentage, allowing for some margin of error.
-
D.
urbanRuralSplit
Indicates a division or distinction between urban and rural areas, conditions, or populations.
-
E.
isLessUrbanizedThan
Indicates that one place has a lower degree of urban development or urban characteristics compared to another place.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb7c000c819094efdcbb23ebddae |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 8:06 p.m.