Triple
T34170906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Federal Reserve District |
E876540
|
entity |
| Predicate | hasKeyPolicyBody |
P190518
|
FINISHED |
| Object | Federal Open Market Committee |
—
|
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: Federal Open Market Committee | Statement: [Second Federal Reserve District, hasKeyPolicyBody, Federal Open Market Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyPolicyBody Context triple: [Second Federal Reserve District, hasKeyPolicyBody, Federal Open Market Committee]
-
A.
hasKeyPolicy
Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
-
B.
hasPolicyBody
Indicates that an entity is associated with, or defined by, a specific policy document or policy text.
-
C.
hasKeyPolicyContext
Indicates that a key is associated with a specific policy context that governs how it may be used, managed, or accessed.
-
D.
hasPolicyDocument
Indicates that an entity is associated with or governed by a specific policy document.
-
E.
hasSignaturePolicy
Indicates that an entity is governed by a specific policy defining rules or requirements for creating, validating, or using signatures.
- F. None of above. chosen
Provenance (4 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 1, 2026, 1:54 a.m.