Triple
T48630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Relief Appropriation Act of 1935 |
E955
|
entity |
| Predicate | enactedIn |
P1127
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Emergency Relief Appropriation Act of 1935, enactedIn, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedIn Context triple: [Emergency Relief Appropriation Act of 1935, enactedIn, 1935]
-
A.
placeOfEnactment
Indicates the location where an event, action, or legal act is formally carried out or put into effect.
-
B.
enactedDuring
chosen
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
C.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
D.
enactedInResponseTo
Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
-
E.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abe7cb481908d969e54032f6c75 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.