Triple
T11007680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ELCH |
E260162
|
entity |
| Predicate | practicesOrdinationOf |
P3467
|
FINISHED |
| Object | pastors |
—
|
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: pastors | Statement: [ELCH, practicesOrdinationOf, pastors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practicesOrdinationOf Context triple: [ELCH, practicesOrdinationOf, pastors]
-
A.
practicesSacrament
Indicates that an entity performs or observes a specific religious sacrament as part of its ritual or faith practice.
-
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.
allowedOrdinationOf
Indicates that one entity permits or authorizes the formal religious ordination of another entity.
-
D.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
E.
ordains
chosen
Indicates that one entity formally appoints or invests another with authority, office, or a religious role through an official or ceremonial act.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79757bdcc8190900b267826eece21 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.