Triple
T4658510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odishi |
E102468
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Abasha |
E102469
|
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: Abasha | Statement: [Odishi, hasTown, Abasha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abasha Context triple: [Odishi, hasTown, Abasha]
-
A.
Abasha
chosen
Abasha is a small town in western Georgia’s Samegrelo region, known as a local administrative and cultural center.
-
B.
Abasa
Abasa is the 80th chapter of the Qur'an, known for its admonition regarding a moment when the Prophet Muhammad frowned at a blind man seeking guidance.
-
C.
Ishbak
Ishbak is a lesser-known son of the biblical patriarch Abraham, mentioned among the children he had later in life.
-
D.
Shawiya
Shawiya refers to an Amazigh (Berber) ethnic group and their Zenati Berber language spoken primarily in the Aurès Mountains of northeastern Algeria.
-
E.
Akhsar
Akhsar is a heroic figure from the Nart sagas, the traditional epic folklore of the peoples of the Caucasus.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd63271a548190bd9662b69a45d9a5 |
completed | March 20, 2026, 3:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdfaf5a0988190b097ef71301aebbe |
completed | March 21, 2026, 1:57 a.m. |
Created at: March 20, 2026, 1:15 p.m.