Triple
T741667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of Mexico |
E15255
|
entity |
| Predicate | constitutionalAutonomy |
P5083
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bank of Mexico, constitutionalAutonomy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionalAutonomy Context triple: [Bank of Mexico, constitutionalAutonomy, yes]
-
A.
grantsOfAutonomy
chosen
Indicates that one entity confers a degree of self-governance, independence, or decision-making authority to another entity.
-
B.
constitutionalPower
Indicates that an entity holds authority or rights granted and defined by a constitution in relation to another entity or domain of action.
-
C.
constitutionalFunction
Indicates that an entity serves a role, duty, or purpose as defined or required by a constitution or foundational governing framework.
-
D.
constitutionalHierarchy
Indicates that one entity holds a superior or subordinate status to another within a formal constitutional or foundational legal framework.
-
E.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
- 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.