Triple
T4327102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monetary Policy Summary |
E96658
|
entity |
| Predicate | publishedAfter |
P46931
|
FINISHED |
| Object | Monetary Policy Committee meeting |
—
|
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: Monetary Policy Committee meeting | Statement: [Monetary Policy Summary, publishedAfter, Monetary Policy Committee meeting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedAfter Context triple: [Monetary Policy Summary, publishedAfter, Monetary Policy Committee meeting]
-
A.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
B.
publishedAtEvent
chosen
Indicates that something (such as a work, announcement, or result) was formally released or made public in connection with a specific event.
-
C.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
D.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
E.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35131f11881909e2d5415a70d5785 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.