Triple
T25174016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Appropriations Bill |
E630396
|
entity |
| Predicate | preparationPrecededBy |
P25144
|
FINISHED |
| Object | budget preparation phase |
—
|
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: budget preparation phase | Statement: [General Appropriations Bill, preparationPrecededBy, budget preparation phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparationPrecededBy Context triple: [General Appropriations Bill, preparationPrecededBy, budget preparation phase]
-
A.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
B.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
C.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
D.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
E.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dbc6fec8190a2ceb4cd781e824d |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:21 p.m.