Triple
T22551941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facultad de Enfermería |
E557578
|
entity |
| Predicate | tieneFuncion |
P61430
|
FINISHED |
| Object | formación de recursos humanos en salud |
—
|
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: formación de recursos humanos en salud | Statement: [Facultad de Enfermería, tieneFuncion, formación de recursos humanos en salud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieneFuncion Context triple: [Facultad de Enfermería, tieneFuncion, formación de recursos humanos en salud]
-
A.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
B.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
C.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
D.
hasServiceFunction
Indicates that an entity performs, provides, or is responsible for a particular service-related function or role.
-
E.
hasFunctionInPresent
chosen
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
- 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_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. |
Created at: April 16, 2026, 8:52 p.m.