Triple
T24767433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Jasso y Azpilicueta |
E619622
|
entity |
| Predicate | isFamilyOfSaint |
P28764
|
FINISHED |
| Object | Francis Xavier |
—
|
NE NERFINISHED |
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: Francis Xavier | Statement: [de Jasso y Azpilicueta, isFamilyOfSaint, Francis Xavier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamilyOfSaint Context triple: [de Jasso y Azpilicueta, isFamilyOfSaint, Francis Xavier]
-
A.
hasLiturgicalFamily
Indicates that one religious rite, tradition, or practice belongs to, or is classified under, a broader liturgical family or lineage.
-
B.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
C.
familyOf
chosen
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
-
E.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:28 a.m.