Triple
T36385430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divus Iulius |
E896180
|
entity |
| Predicate | hasPriestlyOffice |
P103888
|
FINISHED |
| Object | flamen of the Divine Julius |
—
|
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: flamen of the Divine Julius | Statement: [Divus Iulius, hasPriestlyOffice, flamen of the Divine Julius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriestlyOffice Context triple: [Divus Iulius, hasPriestlyOffice, flamen of the Divine Julius]
-
A.
hasReligiousOffice
chosen
Indicates that an entity holds or occupies a specific religious role, position, or office within a religious organization or tradition.
-
B.
isOrdained
Indicates that an entity has been formally conferred religious or clerical authority through an official ordination process.
-
C.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
D.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
E.
hadPriesthood
Indicates that an entity possessed or held a recognized priestly office or religious authority.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.