Triple
T15396853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catalina de Aragón |
E368197
|
entity |
| Predicate | educación |
P85893
|
FINISHED |
| Object | educación humanista |
—
|
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: educación humanista | Statement: [Catalina de Aragón, educación, educación humanista]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: educación Context triple: [Catalina de Aragón, educación, educación humanista]
-
A.
освіта
chosen
Indicates that one entity provides, has, or is associated with the education or educational background of another entity.
-
B.
educationAndCulture
Indicates a relationship where activities, policies, or influences connect educational processes with cultural development, preservation, or expression.
-
C.
educationRight
Indicates that an entity holds a right or entitlement to receive education or educational opportunities.
-
D.
educates
Indicates that one entity provides instruction, knowledge, or training to another entity.
-
E.
educationalSector
Indicates a relationship in which something is part of, associated with, or operates within the education or schooling domain.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8c5d40819086622b70edcb6294 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.