Triple
T10375237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia architectural registration board |
E244489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural registration board |
C12621
|
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: architectural registration board Context triple: [District of Columbia architectural registration board, instanceOf, architectural registration board]
-
A.
architectural association
An architectural association is a professional organization that represents, supports, and regulates the interests, standards, and development of architects and the architectural profession.
-
B.
architects association
chosen
An architects association is a professional organization that represents, supports, and regulates the interests, standards, and development of architects within a specific region or field.
-
C.
architectural qualification
Architectural qualification is the process of evaluating and certifying that a building’s design, materials, and systems meet specified performance, safety, regulatory, and functional requirements.
-
D.
architectural practice
An architectural practice is a professional organization or firm that provides design, planning, and consulting services for the creation, alteration, and evaluation of built environments.
-
E.
architectural congress
An architectural congress is a formal gathering of architects, planners, scholars, and related professionals convened to discuss, present, and debate ideas, projects, and policies shaping the built environment.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:02 p.m.