Triple
T34209944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elagabal |
E877625
|
entity |
| Predicate | highPriest |
P63274
|
FINISHED |
| Object | Elagabalus before becoming emperor |
—
|
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: Elagabalus before becoming emperor | Statement: [Elagabal, highPriest, Elagabalus before becoming emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highPriest Context triple: [Elagabal, highPriest, Elagabalus before becoming emperor]
-
A.
coHighPriestWith
Indicates that two individuals share the role or office of high priest concurrently.
-
B.
notablePriest
Indicates that the subject is recognized as a priest of particular significance or prominence in some context.
-
C.
priests
chosen
Indicates that the subject serves in a religious or spiritual officiating role, typically performing sacred rituals or duties for a faith community.
-
D.
elevatedToPrimatialSee
Indicates that an ecclesiastical jurisdiction or office has been raised in status to become a primatial see, typically granting it senior or leading authority over other sees in a region.
-
E.
successorAsHighPriestOfAmun
Indicates that one individual directly followed another in holding the position of High Priest of Amun.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:55 a.m.