Triple
T3617766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarasios of Constantinople |
E76643
|
entity |
| Predicate | sainthoodStatus |
P20537
|
FINISHED |
| Object | canonized 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: canonized saint | Statement: [Tarasios of Constantinople, sainthoodStatus, canonized saint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sainthoodStatus Context triple: [Tarasios of Constantinople, sainthoodStatus, canonized saint]
-
A.
inCanonizationStatus
chosen
Indicates that an entity has a specific status or stage within a formal canonization process.
-
B.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
C.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
D.
hasPatronSaint
Indicates that one entity serves as the patron saint associated with, protecting, or representing another entity.
-
E.
canonizationDate
Indicates the date on which an individual was officially declared a saint (canonized) by a religious authority.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27dd030819083d34fee0c06612a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.