Triple
T1064744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Elizabeths Hospital (administrative oversight) |
E22983
|
entity |
| Predicate | hasRegulatoryContext |
P12605
|
FINISHED |
| Object | U.S. federal health law |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: U.S. federal health law | Statement: [St. Elizabeths Hospital (administrative oversight), hasRegulatoryContext, U.S. federal health law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulatoryContext Context triple: [St. Elizabeths Hospital (administrative oversight), hasRegulatoryContext, U.S. federal health law]
-
A.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
B.
supportsRegulation
Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
-
C.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
D.
governedByLegalRegime
chosen
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
-
E.
regulatoryDocument
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
- F. None of above.
Provenance (3 batches)
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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b90f91248190ace1534a51b82bdd |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.