Triple
T30847936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gramm–Latta Budget |
E785690
|
entity |
| Predicate | locationOfLegislativeProcess |
P39663
|
FINISHED |
| Object | Washington, D.C. |
—
|
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: Washington, D.C. | Statement: [Gramm–Latta Budget, locationOfLegislativeProcess, Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfLegislativeProcess Context triple: [Gramm–Latta Budget, locationOfLegislativeProcess, Washington, D.C.]
-
A.
hasLegislativeProcess
Indicates that there exists a specific legislative procedure or set of steps governing how laws or regulations are proposed, debated, and enacted for the related entity.
-
B.
usesLegislativeProcess
Indicates that an entity carries out its actions or decisions through a formal legislative procedure, such as proposing, debating, and enacting laws or regulations.
-
C.
legislativeProcessStart
Indicates the point in time or event at which a formal legislative procedure or lawmaking process is initiated.
-
D.
locationOfLegislature
chosen
Indicates the place where a legislature is situated or convenes.
-
E.
coordinatesLegislativeStrategyFor
Indicates that one entity plans, directs, or manages the legislative strategy on behalf of another entity.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
Created at: April 29, 2026, 8:46 p.m.