Triple
T5450550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reglamento Provisorio de 1815 |
E122357
|
entity |
| Predicate | tipoDePolítica |
P55606
|
FINISHED |
| Object | política agraria |
—
|
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: política agraria | Statement: [Reglamento Provisorio de 1815, tipoDePolítica, política agraria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDePolítica Context triple: [Reglamento Provisorio de 1815, tipoDePolítica, política agraria]
-
A.
economicPolicyType
Indicates the classification of an economic policy according to its general type or category (e.g., fiscal, monetary, trade).
-
B.
policyCategory
chosen
Indicates the classification or type of policy under which an item, rule, or action is grouped.
-
C.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
D.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
E.
treatyOrPolicy
Indicates a formal agreement, treaty, or policy that establishes rules, obligations, or guidelines governing the relationship or behavior between entities.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.