Triple
T32482044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.R. 1 (110th Congress) |
E830136
|
entity |
| Predicate | post9_11Reform |
P10613
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [H.R. 1 (110th Congress), post9_11Reform, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: post9_11Reform Context triple: [H.R. 1 (110th Congress), post9_11Reform, yes]
-
A.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
B.
postReformDevelopment
chosen
Indicates the development or changes that occur after a reform has been implemented.
-
C.
scriptAfterReform
Indicates that one script or writing system is used after a reform or modification has been applied to another script.
-
D.
functionAfterReformation
Indicates that one function or role exists or is performed in the state or period following a process of reformation or reform.
-
E.
seeksToReform
Indicates an entity’s intention or effort to change an existing system, practice, or condition in order to improve or correct it.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3962bd4819095fc94002d3f5247 |
completed | May 3, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:58 a.m.