Triple
T10625063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 99-177 |
E250300
|
entity |
| Predicate | timePeriodTargeted |
P302
|
FINISHED |
| Object | late 1980s federal budgets |
—
|
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: late 1980s federal budgets | Statement: [Public Law 99-177, timePeriodTargeted, late 1980s federal budgets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodTargeted Context triple: [Public Law 99-177, timePeriodTargeted, late 1980s federal budgets]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
C.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
-
D.
timePeriodAnalyzed
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
-
E.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7fe9fc81908b3b8d1dc06a829c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:53 p.m.