Triple
T5446442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edom |
E122259
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Bozrah |
E521043
|
NE 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: Bozrah | Statement: [Edom, majorCity, Bozrah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bozrah Context triple: [Edom, majorCity, Bozrah]
-
A.
Bozrah
chosen
Bozrah was an important ancient city that served as the principal stronghold and royal center of the kingdom of Edom, located south of the Dead Sea.
-
B.
Heshbon
Heshbon is an ancient city in the Transjordan region frequently mentioned in the Bible as a significant Moabite and later Israelite center.
-
C.
Erechim
Erechim is a city in southern Brazil known for its strong German-Brazilian cultural heritage and influence.
-
D.
Talfah
Talfah is an Iraqi family name most prominently associated with Sajida Talfah, the first wife of former Iraqi president Saddam Hussein.
-
E.
Rabbath Ammon
Rabbath Ammon was the ancient capital of the Ammonite kingdom, located on the site of modern-day Amman in present-day Jordan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd91cf5d488190868ffefad02c7a04 |
completed | March 20, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf4881d6308190a4e7cb784eb520c9 |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:07 p.m.