Triple
T31311822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doda of Metz |
E798482
|
entity |
| Predicate | spouseCanonizationStatus |
P20537
|
FINISHED |
| Object | saint |
—
|
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: saint | Statement: [Doda of Metz, spouseCanonizationStatus, saint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseCanonizationStatus Context triple: [Doda of Metz, spouseCanonizationStatus, saint]
-
A.
spouseOfSaint
Indicates that one entity is the husband or wife of a person recognized as a saint.
-
B.
dateOfCanonizationStatus
Indicates the date on which an entity’s canonization status (such as being declared a saint or blessed) was formally conferred or recorded.
-
C.
spouseVeneratedAs
Indicates that one person’s spouse is regarded or honored with special reverence, respect, or worship by that person.
-
D.
inCanonizationStatus
chosen
Indicates that an entity has a specific status or stage within a formal canonization process.
-
E.
canonizationType
Indicates the specific manner or category by which an individual is formally recognized as a saint or holy figure within a religious canon.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 29, 2026, 9:15 p.m.