Triple
T32788277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels liaison office |
E838556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | representative outpost |
C59177
|
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: representative outpost Context triple: [Brussels liaison office, instanceOf, representative outpost]
-
A.
colonial-era trading outpost
A colonial-era trading outpost is a remote settlement established by an imperial power to facilitate the exchange of goods, resources, and information between the colonizing nation and local populations, often serving as a strategic hub for commerce, governance, and cultural contact.
-
B.
frontier post
A frontier post is a fortified or administrative outpost located at the edge of a state’s or empire’s territory, serving to monitor, defend, and control movement across its borders.
-
C.
colonial stronghold
A colonial stronghold is a heavily fortified settlement or military outpost established by a colonizing power to secure control, protect resources, and project authority over a foreign territory.
-
D.
Dutch trading post
A Dutch trading post is a commercial outpost established by the Dutch, primarily during the 17th and 18th centuries, to facilitate trade, resource extraction, and colonial administration in foreign territories.
-
E.
Cossack stanitsa
A Cossack stanitsa is a traditional self-governing Cossack village or settlement that served as both an administrative unit and a military community on the frontiers of the Russian Empire.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.