Triple
T25684946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Census of India |
E644040
|
entity |
| Predicate | mostPopulousUnionTerritory |
P159183
|
FINISHED |
| Object | Delhi |
—
|
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: Delhi | Statement: [2011 Census of India, mostPopulousUnionTerritory, Delhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostPopulousUnionTerritory Context triple: [2011 Census of India, mostPopulousUnionTerritory, Delhi]
-
A.
borderingUnionTerritory
Indicates that one entity shares a land or maritime boundary with a specified Union Territory.
-
B.
locationUnionTerritory
Indicates that a location is situated within, or is part of, a specific union territory.
-
C.
governingUnionTerritory
Indicates that a specified union territory is the administrative jurisdiction governing or responsible for another entity.
-
D.
unionTerritoryWithoutLegislature
Indicates that a union territory exists under central administration without having its own legislative assembly or lawmaking body.
-
E.
wasUnionTerritoryAs
Indicates that an entity held the status of a union territory during a specified time or under specified conditions.
- 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_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_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 8:06 p.m.