Triple
T37089084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicepresidencia de Administración |
E918366
|
entity |
| Predicate | apoyaA |
P187130
|
FINISHED |
| Object | funcionamiento interno del organismo regulador |
—
|
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: funcionamiento interno del organismo regulador | Statement: [Vicepresidencia de Administración, apoyaA, funcionamiento interno del organismo regulador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apoyaA Context triple: [Vicepresidencia de Administración, apoyaA, funcionamiento interno del organismo regulador]
-
A.
apodo
Indicates that one entity serves as a nickname or alias by which another entity is commonly known.
-
B.
pakad
Indicates the act of catching, holding, or seizing someone or something, typically by grasping or capturing it.
-
C.
пол
Indicates a relationship specifying an entity’s sex or gender classification.
-
D.
areA
Indicates that one entity is classified as a type, instance, or member of another entity or category.
-
E.
porte
Indicates that an entity carries, wears, or bears another entity (such as an object, attribute, or characteristic).
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.