Triple
T30680136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herodian tetrarchy |
E781029
|
entity |
| Predicate | hasSuccessorRuler |
P45012
|
FINISHED |
| Object | Herod Archelaus |
—
|
NE NERFINISHED |
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: Herod Archelaus | Statement: [Herodian tetrarchy, hasSuccessorRuler, Herod Archelaus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorRuler Context triple: [Herodian tetrarchy, hasSuccessorRuler, Herod Archelaus]
-
A.
successorRuler
chosen
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
B.
successorEraRuler
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
-
C.
hasFormerRuler
Indicates that an entity previously served as the ruler of another entity but no longer holds that ruling position.
-
D.
successorAsCoRulerOf
Indicates that one entity became the next co-ruler alongside another entity, following a previous co-ruler in a shared rulership position.
-
E.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 29, 2026, 8:32 p.m.