Triple
T6432388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Fisher |
E129807
|
entity |
| Predicate | hasCanonizationReason |
P25961
|
FINISHED |
| Object | martyrdom for the Catholic faith |
—
|
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: martyrdom for the Catholic faith | Statement: [John Fisher, hasCanonizationReason, martyrdom for the Catholic faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonizationReason Context triple: [John Fisher, hasCanonizationReason, martyrdom for the Catholic faith]
-
A.
hasCanonization
Indicates that an entity has undergone or been granted formal canonization, typically recognizing it as officially sainted or sanctified.
-
B.
hasPartInCanonization
Indicates that an entity participated in or contributed to the process of canonization of another entity.
-
C.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
-
D.
reasonForCanonization
chosen
Indicates the specific cause, miracle, virtue, or event that served as the basis for a person’s canonization.
-
E.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693de6ac81909f3e330363a52102 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.