Triple
T15787756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aka-Bea |
E382780
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Aka-Kol |
E382782
|
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: Aka-Kol | Statement: [Aka-Bea, relatedTo, Aka-Kol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aka-Kol Context triple: [Aka-Bea, relatedTo, Aka-Kol]
-
A.
Aka-Kol
chosen
Aka-Kol is an extinct Great Andamanese language once spoken by the indigenous Kol people of the Andaman Islands in India.
-
B.
Pishpek
Pishpek, now known as Bishkek, is the capital and largest city of Kyrgyzstan in Central Asia.
-
C.
Yakut
Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
-
D.
Anadyr
Anadyr is a remote Arctic port town in Russia’s Far East, situated on the Anadyr River near the Bering Sea and serving as the main administrative, economic, and cultural center of the surrounding region.
-
E.
Khatanga
Khatanga is a remote Arctic port settlement in northern Siberia, Russia, serving as a key access point to the Laptev Sea and surrounding tundra regions.
- 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_69e054048ff48190ad107c890ef73166 |
completed | April 16, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa12d6f388190b61cdc7820ce6311 |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 10, 2026, 4:48 a.m.