Triple
T27637923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.R.34 |
E696514
|
entity |
| Predicate | hasRegulatoryBodyAffected |
P24019
|
FINISHED |
| Object | U.S. Food and Drug Administration |
—
|
NE NERFINISHED |
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. Food and Drug Administration | Statement: [H.R.34, hasRegulatoryBodyAffected, U.S. Food and Drug Administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulatoryBodyAffected Context triple: [H.R.34, hasRegulatoryBodyAffected, U.S. Food and Drug Administration]
-
A.
hasRegulatoryOrCulturalBody
Indicates that an entity is overseen, guided, or influenced by a formal regulatory authority or a culturally significant governing body.
-
B.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
C.
governingBodyImpacted
chosen
Indicates that a governing body is affected or influenced by a particular action, event, or condition.
-
D.
regulationImpact
Indicates how a regulation influences, constrains, or alters the behavior, performance, or outcomes associated with the related entities.
-
E.
hasRegulatoryMarket
Indicates that an entity is subject to, or operates within, a specific regulatory framework or market oversight regime.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: April 27, 2026, 2:24 p.m.