Triple
T12475846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sub-treasury in New Orleans |
E298174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional financial office |
C1183
|
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 financial office Context triple: [sub-treasury in New Orleans, instanceOf, regional financial office]
-
A.
regional administrative branch
chosen
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.
-
B.
international financial institution office
An international financial institution office is a local or regional branch of a global financial organization that manages and coordinates its financial services, policy implementation, and stakeholder relations within a specific geographic area.
-
C.
regional development fund
A regional development fund is a financial mechanism that pools and allocates resources to support economic growth, infrastructure, and social development projects within a specific geographic area.
-
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 development bank
A regional development bank is a multilateral financial institution that provides loans, grants, and technical assistance to support economic and social development within a specific geographic region.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.