Triple
T4384607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatha |
E99210
|
entity |
| Predicate | hasGaelicName |
P8668
|
FINISHED |
| Object | Tatha |
E99210
|
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: Tatha | Statement: [Tatha, hasGaelicName, Tatha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tatha Context triple: [Tatha, hasGaelicName, Tatha]
-
A.
Tatha
chosen
Tatha is the Scottish Gaelic name for the River Tay, one of Scotland’s longest and most significant rivers.
-
B.
Tawthalin
Tawthalin is a traditional month in the Burmese calendar, associated with late monsoon season and various cultural and religious observances in Myanmar.
-
C.
Batha
Batha is a central region of Chad known for its semi-arid Sahelian landscape and traditional pastoralist communities.
-
D.
Shivta
Shivta is an ancient Nabatean and Byzantine desert city in Israel, known for its remarkably well-preserved ruins and role along historic trade routes.
-
E.
Udaya
Udaya is a given name most notably associated with D. Udaya Kumar, the Indian designer who created the Indian rupee sign.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5e523cc5c8190b9884f83d433982c |
completed | March 14, 2026, 10:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.