Triple
T11929349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 110-417 |
E283869
|
entity |
| Predicate | hasFiscalYearCoverage |
P102202
|
FINISHED |
| Object | Fiscal Year 2009 |
—
|
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: Fiscal Year 2009 | Statement: [Public Law 110-417, hasFiscalYearCoverage, Fiscal Year 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFiscalYearCoverage Context triple: [Public Law 110-417, hasFiscalYearCoverage, Fiscal Year 2009]
-
A.
fiscalYearHonored
Indicates that a particular fiscal year is formally recognized, celebrated, or given special acknowledgment in relation to an entity or event.
-
B.
fiscalYearEnd
Indicates the date or point in time when an entity’s fiscal or financial reporting year concludes.
-
C.
hasFrequencyCoverage
Indicates that one entity provides, supports, or is applicable across a specified range or set of frequencies associated with another entity.
-
D.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
E.
fiscalYearStartInfluence
Indicates how the start date or structure of a fiscal year affects or shapes a related process, condition, or outcome.
- F. None of above. chosen
Provenance (4 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90303a9a88190a4044e6310ba9b4b |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.