Triple
T22551920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facultad de Enfermería |
E557578
|
entity |
| Predicate | tieneMision |
P107026
|
FINISHED |
| Object | formación universitaria en enfermería |
—
|
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 universitaria en enfermería | Statement: [Facultad de Enfermería, tieneMision, formación universitaria en enfermería]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieneMision Context triple: [Facultad de Enfermería, tieneMision, formación universitaria en enfermería]
-
A.
tieneMisión
chosen
Indicates that an entity is assigned or carries out a specific mission or task.
-
B.
hasMissionIn
Indicates that an entity carries out, undertakes, or is assigned a mission within a specified location or region.
-
C.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
D.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
E.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
- 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.