Triple
T6006689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 93-383 |
E133726
|
entity |
| Predicate | sectionReference |
P14593
|
FINISHED |
| Object | Title I – Community Development |
—
|
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: Title I – Community Development | Statement: [Public Law 93-383, sectionReference, Title I – Community Development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionReference Context triple: [Public Law 93-383, sectionReference, Title I – Community Development]
-
A.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
sectionAddressed
chosen
Indicates that a specific section or part of a document, text, or resource is being referred to, targeted, or dealt with by an action or statement.
-
C.
sectionType
Indicates the specific kind or category of section that an entity belongs to or represents.
-
D.
articleReference
Indicates that one entity cites, mentions, or refers to another entity within an article or written document.
-
E.
regionReference
Indicates that one entity refers to, points to, or is associated with a specific region or area defined by 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f13d9908190a11d9bef8652db93 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.