Triple
T2897970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Unemployment Tax Act |
E63986
|
entity |
| Predicate | subjectToChangeBy |
P1121
|
FINISHED |
| Object | subsequent federal legislation |
—
|
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: subsequent federal legislation | Statement: [Federal Unemployment Tax Act, subjectToChangeBy, subsequent federal legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToChangeBy Context triple: [Federal Unemployment Tax Act, subjectToChangeBy, subsequent federal legislation]
-
A.
amendedBy
chosen
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
B.
decorChangedBy
Indicates that a change in decor or visual appearance was caused or brought about by a specific entity or action.
-
C.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
D.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe08fe3248190a6bb7de2a2c317b1 |
completed | March 7, 2026, 8:23 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:08 p.m.