Triple
T37315058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instituto de Salud para el Bienestar |
E926310
|
entity |
| Predicate | ámbito de actuación |
P111844
|
FINISHED |
| Object | nacional |
—
|
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: nacional | Statement: [Instituto de Salud para el Bienestar, ámbito de actuación, nacional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ámbito de actuación Context triple: [Instituto de Salud para el Bienestar, ámbito de actuación, nacional]
-
A.
ambito
Indicates the domain, scope, or contextual sphere within which a relation, action, or condition holds.
-
B.
area of activity
chosen
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
C.
scopeOfDuty
Indicates the range or extent of responsibilities, tasks, or obligations that an entity is expected or authorized to perform.
-
D.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
E.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.