Triple
T741668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of Mexico |
E15255
|
entity |
| Predicate | primaryMandate |
P11083
|
FINISHED |
| Object | price stability |
—
|
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: price stability | Statement: [Bank of Mexico, primaryMandate, price stability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMandate Context triple: [Bank of Mexico, primaryMandate, price stability]
-
A.
mandateFrom
Indicates that one entity has been granted authoritative permission or instruction by another entity to act or decide on its behalf.
-
B.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
C.
hasMandate
chosen
Indicates that an entity is officially authorized or required to perform a specific role, action, or set of responsibilities.
-
D.
primaryVows
Indicates that an entity has made or is bound by its main or foundational vows, promises, or commitments in a given context.
-
E.
primarySettingOf
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60e286c81908787a41cf9b9f150 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.