Triple
T22551937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facultad de Enfermería |
E557578
|
entity |
| Predicate | ambito |
P148625
|
FINISHED |
| Object | salud pública |
—
|
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: salud pública | Statement: [Facultad de Enfermería, ambito, salud pública]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambito Context triple: [Facultad de Enfermería, ambito, salud pública]
-
A.
aria
Indicates that an entity is associated with ARIA (Accessible Rich Internet Applications) attributes or roles that define how it should be interpreted by assistive technologies.
-
B.
aspect
Indicates a specific temporal phase or manner in which an action, event, or state unfolds or is viewed (e.g., ongoing, completed, habitual).
-
C.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
D.
area
Indicates that one entity has a measured two-dimensional extent or surface size quantified by another entity.
-
E.
agency
Indicates that an entity acts on behalf of, represents, or exercises power or control for another entity in performing an action or fulfilling a role.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7647208190a1aaebd083bf095a |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:52 p.m.