Triple
T5325393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Housing Agency |
E121771
|
entity |
| Predicate | regulatoryRequirement |
P9279
|
FINISHED |
| Object | comply with HUD regulations |
—
|
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: comply with HUD regulations | Statement: [Public Housing Agency, regulatoryRequirement, comply with HUD regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryRequirement Context triple: [Public Housing Agency, regulatoryRequirement, comply with HUD regulations]
-
A.
regulatoryStandard
Indicates that one entity serves as an official rule, guideline, or benchmark that governs, constrains, or evaluates the behavior, quality, or performance of another entity.
-
B.
regulatoryDocument
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
-
C.
legalRequirement
chosen
Indicates that one entity is obligated by law to perform, provide, or comply with something in relation to another entity or situation.
-
D.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
E.
relatedRegulation
Indicates that there exists a regulatory rule, law, or directive that is associated with, governs, or is otherwise relevant to the referenced entity or activity.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 1:59 p.m.