Triple
T5769273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Security Administration headquarters complex |
E127287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal office building complex |
C127
|
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: federal office building complex Context triple: [Social Security Administration headquarters complex, instanceOf, federal office building complex]
-
A.
federal compound
A federal compound is a secured complex of buildings and facilities owned or operated by a national government, typically used for administrative, judicial, law enforcement, or detention purposes under federal jurisdiction.
-
B.
civic building complex
A civic building complex is a coordinated group of public structures and spaces designed to house governmental, administrative, and community services within a unified physical setting.
-
C.
office building complex
chosen
An office building complex is a group of interconnected or closely situated office structures designed to provide workspace, shared amenities, and supporting services for multiple businesses or organizations.
-
D.
government building
A government building is a structure owned or used by a public authority to house offices, services, and functions related to the administration and governance of a city, region, or country.
-
E.
state government complex
A state government complex is a centralized group of buildings and facilities where a state's executive, legislative, and often judicial branches conduct official governmental operations and public services.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:50 p.m.