Triple
T4020264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyrcanus II |
E91262
|
entity |
| Predicate | highPriesthoodStart |
P14734
|
FINISHED |
| Object | 76 BCE |
—
|
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: 76 BCE | Statement: [Hyrcanus II, highPriesthoodStart, 76 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highPriesthoodStart Context triple: [Hyrcanus II, highPriesthoodStart, 76 BCE]
-
A.
hadPriesthood
Indicates that an entity possessed or held a recognized priestly office or religious authority.
-
B.
wasOrdainedAs
chosen
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
C.
beganTermAsPresidingBishopOn
Indicates the date on which an individual started their term serving in the role of Presiding Bishop.
-
D.
startingTemple
Indicates that an entity serves as the initial or origin temple associated with another entity or process.
-
E.
hasBishopric
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.