Triple
T34416817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrine ministry |
E883420
|
entity |
| Predicate | entrustedBy |
P96404
|
FINISHED |
| Object | Jesus Christ |
—
|
NE NERFINISHED |
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: Jesus Christ | Statement: [Petrine ministry, entrustedBy, Jesus Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entrustedBy Context triple: [Petrine ministry, entrustedBy, Jesus Christ]
-
A.
entrustedTo
chosen
Indicates that responsibility, care, or control of something has been formally given by one party to another.
-
B.
heldInTrustFor
Indicates that one party holds an asset, right, or interest on behalf of and for the benefit of another party, subject to fiduciary or trust obligations.
-
C.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
D.
laterCommissionedBy
Indicates that one entity was commissioned at a later time by another entity, establishing a commissioning relationship that occurred after an earlier reference point or event.
-
E.
gainsTrustOf
Indicates that one entity comes to be regarded as trustworthy by another entity, earning that other entity’s confidence or reliance.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.