Triple
T23059035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Kozłowiecki |
E574243
|
entity |
| Predicate | wasOrdainedPriestIn |
P14734
|
FINISHED |
| Object | 1937 |
—
|
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: 1937 | Statement: [Adam Kozłowiecki, wasOrdainedPriestIn, 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOrdainedPriestIn Context triple: [Adam Kozłowiecki, wasOrdainedPriestIn, 1937]
-
A.
wasOrdainedAs
chosen
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
B.
ordainedIn
Indicates that an individual was formally appointed or consecrated to a religious office or role at a specific place or within a particular institution.
-
C.
ordainedFor
Indicates that one entity has been formally appointed or consecrated to serve, function, or act on behalf of another entity or purpose.
-
D.
ordainedBy
Indicates that an entity has been formally appointed, consecrated, or invested with authority by another entity.
-
E.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1899e6c788190a2a862122cae8dc3 |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.