Triple
T29624081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissariat Store |
E755082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era supply store |
C9477
|
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 supply store Context triple: [Commissariat Store, instanceOf, colonial-era supply store]
-
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.
historic general store
chosen
A historic general store is a preserved or restored retail establishment that once served as a community hub, offering a wide variety of everyday goods and services reflective of a specific past era.
-
C.
colonial-era trade corridor
A colonial-era trade corridor is a strategically established route or network used during colonial times to transport goods, people, and resources between colonies and imperial centers, shaping economic patterns and cultural exchanges.
-
D.
lumber company store
A lumber company store is a retail establishment, often owned by a lumber producer, that sells wood products, building materials, and related supplies to contractors, builders, and the general public.
-
E.
colonial bank
A colonial bank is a financial institution established in a colony, typically by or under the authority of a colonial power, to manage currency, credit, and trade in support of imperial economic interests.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:36 p.m.