Triple
T21189582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 113-79 |
E522176
|
entity |
| Predicate | fiscalCoverageEnd |
P110778
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Public Law 113-79, fiscalCoverageEnd, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiscalCoverageEnd Context triple: [Public Law 113-79, fiscalCoverageEnd, 2018]
-
A.
endYearCovered
chosen
Indicates the year in which a specified coverage, period, or applicability comes to an end.
-
B.
chronologicalCoverageEnd
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
-
C.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
D.
governedPeriodEnd
Indicates the point in time at which a governing authority’s control or jurisdiction over something comes to an end.
-
E.
hasFiscalYearCoverage
Indicates that one entity’s applicable period, data, or responsibility spans or corresponds to a specified fiscal year or range of fiscal years.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733350e588190a31467758a8afa5c |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.