Triple
T17552558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia River Department |
E427504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional trading division |
C2248
|
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: regional trading division Context triple: [Columbia River Department, instanceOf, regional trading division]
-
A.
trading and sales division
The trading and sales division is a business unit responsible for executing financial market transactions and providing market access, products, and advisory services to clients to facilitate investment, hedging, and financing activities.
-
B.
regional division
chosen
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
C.
regional trade union
A regional trade union is an organization that represents and advocates for the collective interests, rights, and working conditions of workers within a specific geographic region or group of neighboring countries.
-
D.
regional center
A regional center is an organization or facility that provides specialized services, coordination, and support to a defined geographic area, often acting as a hub for resources, administration, or expertise.
-
E.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.