Triple
T32712623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prałatura Sanctae Crucis et Operis Dei |
E836438
|
entity |
| Predicate | hasFounderCanonizedAs |
P194479
|
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: [Prałatura Sanctae Crucis et Operis Dei, hasFounderCanonizedAs, saint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderCanonizedAs Context triple: [Prałatura Sanctae Crucis et Operis Dei, hasFounderCanonizedAs, saint]
-
A.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
-
B.
hasFounderRelationship
Indicates a relationship where one entity serves as the founder or co-founder of another entity.
-
C.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
-
D.
hasFounderName
Indicates that an entity has a founder whose personal name is given by the associated value.
-
E.
hasFounderCharacter
Indicates that an entity has a founder who possesses a specified character trait or set of personal qualities.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: May 1, 2026, 1:11 a.m.