Triple
T2564115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian saints |
E57309
|
entity |
| Predicate | hasProcessOfRecognition |
P40224
|
FINISHED |
| Object | canonization |
—
|
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: canonization | Statement: [Christian saints, hasProcessOfRecognition, canonization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessOfRecognition Context triple: [Christian saints, hasProcessOfRecognition, canonization]
-
A.
recognitionStatus
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
-
B.
canRecognize
Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
-
C.
formOfRecognition
Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to another entity.
-
D.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
-
E.
resultRecognizedBy
Indicates that a particular result is formally acknowledged, validated, or accepted by a specified recognizing entity.
- F. None of above. chosen
Provenance (4 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:48 p.m.