Triple
T24183005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanleyville |
E599475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era place name |
C4613
|
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-era place name Context triple: [Stanleyville, instanceOf, colonial-era place name]
-
A.
historical place name
chosen
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
B.
Aboriginal place name
An Aboriginal place name is a geographic name derived from the languages and cultural traditions of Indigenous Australian peoples, often reflecting features of the land, water, flora, fauna, or ancestral stories associated with that location.
-
C.
Native American place name
A Native American place name is a geographic name derived from the languages and naming traditions of Indigenous peoples of the Americas, often reflecting local features, history, or cultural significance.
-
D.
colonial-era monument
A colonial-era monument is a public structure or statue erected during or commemorating a period of colonial rule, symbolizing the power, values, and historical narratives of the colonizing authority.
-
E.
former colonial settlement
A former colonial settlement is a community or territory originally established and governed by a foreign colonial power that has since transitioned to local or independent control, often retaining cultural, architectural, and institutional legacies of its colonial past.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:34 p.m.