Triple
T25174003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Appropriations Bill |
E630396
|
entity |
| Predicate | stageAfterPassage |
P157991
|
FINISHED |
| Object | General Appropriations Act |
—
|
NE NERFINISHED |
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: General Appropriations Act | Statement: [General Appropriations Bill, stageAfterPassage, General Appropriations Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageAfterPassage Context triple: [General Appropriations Bill, stageAfterPassage, General Appropriations Act]
-
A.
stageAfter
Indicates that one stage occurs later in sequence or order than another specified stage.
-
B.
stageReached
Indicates that a process, task, or entity has arrived at or completed a specific stage or phase within a defined progression.
-
C.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
stageReachedByWinner
Indicates the competition stage that the eventual winner had reached or achieved.
-
E.
stageCriterion
Indicates that a specific condition or requirement is used to determine or classify the stage or phase of a process, object, or entity.
- 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_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. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:21 p.m.