Triple
T2497875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Epistle to Timothy |
E52393
|
entity |
| Predicate | recipientRole |
P18936
|
FINISHED |
| Object | young church leader |
—
|
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: young church leader | Statement: [First Epistle to Timothy, recipientRole, young church leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recipientRole Context triple: [First Epistle to Timothy, recipientRole, young church leader]
-
A.
beneficiaryRole
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by another entity.
-
B.
primaryRecipient
chosen
Indicates the entity that is the main or principal receiver of something, such as a message, resource, or benefit, in a given context.
-
C.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
D.
recipientOccupation
Indicates that the object specifies the job, profession, or role held by the recipient in the described relationship or event.
-
E.
receiverType
Indicates the category or classification of the entity that receives something (such as a message, resource, or action) in the relationship.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ad2f8c81908853e97d75081e84 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.