Triple
T23357152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abiathar |
E593079
|
entity |
| Predicate | servedAsPriestDuring |
P151999
|
FINISHED |
| Object | reign of King David |
—
|
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: reign of King David | Statement: [Abiathar, servedAsPriestDuring, reign of King David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsPriestDuring Context triple: [Abiathar, servedAsPriestDuring, reign of King David]
-
A.
workedAsClergymanIn
Indicates that a person served in a religious or clerical role within a specified place or institution.
-
B.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
C.
servedInDiocese
Indicates that one entity held a role or performed official duties within the jurisdiction of a particular diocese.
-
D.
heldEcclesiasticalAuthorityIn
Indicates that an entity possessed official religious or church authority within a specified place or jurisdiction.
-
E.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a18996c81909c7ad15cde616553 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:28 p.m.