Triple
T5256811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idoumaia |
E118719
|
entity |
| Predicate | HerodTheGreatOrigin |
P1823
|
FINISHED |
| Object | Idumean descent |
—
|
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: Idumean descent | Statement: [Idoumaia, HerodTheGreatOrigin, Idumean descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HerodTheGreatOrigin Context triple: [Idoumaia, HerodTheGreatOrigin, Idumean descent]
-
A.
officeStartAsPatriarchOfAlexandria
Indicates the time or event at which an individual begins their tenure serving as the Patriarch of Alexandria.
-
B.
predecessorAsEasternAugustus
Indicates that one entity previously held the position of Eastern Roman Emperor immediately before the other entity.
-
C.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
D.
PtolemaicSideLedBy
Indicates that a particular side or faction in a Ptolemaic context is under the leadership or command of a specified leader.
-
E.
officeEndAsPatriarchOfAlexandria
Indicates the time or event at which a person’s tenure as Patriarch of Alexandria comes to an end.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ba4ecd88190800b5e4eea3abed5 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.