Triple
T20658186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azarias |
E507681
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Azariah |
—
|
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: Azariah | Statement: [Azarias, hasVariantSpelling, Azariah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Azariah Context triple: [Azarias, hasVariantSpelling, Azariah]
-
A.
Azariah
Azariah is a biblical figure portrayed as one of the three youths delivered by God from the fiery furnace in the Book of Daniel and related deuterocanonical additions.
-
B.
Azariah
Azariah is another name for Uzziah, a king of Judah in the Hebrew Bible known for his long and prosperous reign before being struck with leprosy.
-
C.
Azariah the priest
Azariah the priest was a high priest in ancient Judah, noted in the Bible for courageously confronting King Uzziah when the king unlawfully attempted to burn incense in the temple.
-
D.
Shemaiah
Shemaiah is a biblical figure known primarily as the father of Uriah mentioned in the Hebrew Bible.
-
E.
Hoshea
Hoshea was the last king of the northern Kingdom of Israel, whose reign ended with the Assyrian conquest and the kingdom’s destruction in the 8th century BCE.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
Provenance (2 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
Created at: April 16, 2026, 11:43 a.m.