Triple
T10964647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | semiannual Humphrey–Hawkins testimony |
E259063
|
entity |
| Predicate | regarding |
P54588
|
FINISHED |
| Object | short-term interest rate policy |
—
|
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: short-term interest rate policy | Statement: [semiannual Humphrey–Hawkins testimony, regarding, short-term interest rate policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regarding Context triple: [semiannual Humphrey–Hawkins testimony, regarding, short-term interest rate policy]
-
A.
regards
chosen
Indicates that one entity considers, views, or treats another entity in a particular way or with a certain attitude.
-
B.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
C.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
D.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
E.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77148c4588190ad0f2b54ee4bab98 |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.