Triple
T34610581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byrd Unit |
E888719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intake and diagnostic center |
C38114
|
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: intake and diagnostic center Context triple: [Byrd Unit, instanceOf, intake and diagnostic center]
-
A.
intake and reception center
chosen
An intake and reception center is a facility where individuals first arrive to be registered, assessed, and oriented before being assigned or transferred to appropriate services or longer-term placements.
-
B.
outpatient care facility
An outpatient care facility is a healthcare center where patients receive diagnostic, therapeutic, or preventive medical services without being admitted for an overnight stay.
-
C.
U.S. Food and Drug Administration center
A U.S. Food and Drug Administration center is a specialized organizational unit within the FDA responsible for regulating and overseeing specific categories of products, such as drugs, biologics, medical devices, or food, to ensure their safety, effectiveness, and proper labeling.
-
D.
tertiary care center
A tertiary care center is a specialized healthcare facility that provides advanced, highly specialized diagnostic, therapeutic, and surgical services typically unavailable at primary or secondary care institutions.
-
E.
specialty medical center
A specialty medical center is a healthcare facility focused on diagnosing, treating, and managing conditions within a specific medical field or group of related specialties, often offering advanced expertise and technology.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.