Triple
T37088508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sistema de Administración Financiera Federal |
E918352
|
entity |
| Predicate | procesoCubierto |
P98403
|
FINISHED |
| Object | programación del gasto público federal |
—
|
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: programación del gasto público federal | Statement: [Sistema de Administración Financiera Federal, procesoCubierto, programación del gasto público federal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: procesoCubierto Context triple: [Sistema de Administración Financiera Federal, procesoCubierto, programación del gasto público federal]
-
A.
cobertura
Indicates that one entity provides coverage, protection, or a covering layer over another entity.
-
B.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
C.
broaderProcess
chosen
Indicates that one process encompasses, includes, or provides the larger context for another, more specific process.
-
D.
categoryCovered
Indicates that one category is included within, addressed by, or encompassed under the scope of another entity or context.
-
E.
documentedProcess
Indicates that a process has been formally recorded, described, or specified in documentation.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.