Triple
T15802781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bashan |
E383136
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Hauran |
E571616
|
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: Hauran | Statement: [Bashan, borderedBy, Hauran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hauran Context triple: [Bashan, borderedBy, Hauran]
-
A.
Hauran
chosen
Hauran is a historical region in southwestern Syria and northwestern Jordan, known for its fertile volcanic plains and ancient settlements.
-
B.
Harauti
Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
-
C.
Horki
Horki is a town in eastern Belarus known for its agricultural academy and regional administrative significance.
-
D.
Wurtulla
Wurtulla is a coastal suburb on Queensland’s Sunshine Coast in Australia, known for its long sandy beaches and residential communities.
-
E.
Harestua
Harestua is a village in Viken county, Norway, known for its residential community and proximity to the Harestua Solar Observatory.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b523bf508190af4a54bdc983a9a1 |
completed | April 16, 2026, 10:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff998b52e481908baa20b5a8c1cbcf |
completed | May 9, 2026, 8:31 p.m. |
Created at: April 10, 2026, 4:48 a.m.