Triple
T16513301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlalpan (neighborhood) |
E401116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial district |
C37564
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: colonial district Context triple: [Tlalpan (neighborhood), instanceOf, colonial district]
-
A.
colonial territory
A colonial territory is a geographic area under the political control and administration of a distant foreign power, typically exploited for economic, strategic, or settlement purposes.
-
B.
district of British India
A district of British India was an administrative subdivision governed by colonial authorities, typically comprising multiple towns and villages, used for managing revenue collection, law and order, and local governance under the British Raj.
-
C.
colonial city
A colonial city is an urban settlement established or significantly reshaped by a foreign colonial power, typically characterized by imposed administrative, economic, and cultural structures that reflect the colonizer’s interests more than those of the indigenous population.
-
D.
pre-colonial territory
A pre-colonial territory is a geographically defined area governed, used, or inhabited by indigenous or local societies before the imposition of foreign colonial rule and boundaries.
-
E.
colonial government
A colonial government is the political and administrative system imposed by a foreign power to control and manage a colony’s territory, resources, and population, typically subordinating local authority to the interests of the colonizing state.
- F. None of above. chosen
Provenance (1 batch)
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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:14 a.m.