Triple
T10761256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape to Cairo Railway project |
E253831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial infrastructure project |
C2938
|
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 infrastructure project Context triple: [Cape to Cairo Railway project, instanceOf, colonial infrastructure project]
-
A.
infrastructure project
chosen
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
-
B.
colonial enterprise
A colonial enterprise is an organized venture, typically led by a state or chartered company, that establishes control over foreign territories and peoples to extract resources, labor, and strategic advantage.
-
C.
colonial estate
A colonial estate is a large property established during a colonial period, typically featuring expansive landholdings, a grand main residence, and outbuildings used for agriculture, administration, and housing laborers.
-
D.
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.
-
E.
colonial policy
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
- F. None of above.
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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:16 p.m.