Triple
T2888804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dila |
E59569
|
entity |
| Predicate | basedIn |
P40
|
FINISHED |
| Object | Gori |
E1743
|
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: Gori | Statement: [Dila, basedIn, Gori]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gori Context triple: [Dila, basedIn, Gori]
-
A.
Gori
chosen
Gori is a city in central Georgia best known as the birthplace of Soviet leader Joseph Stalin.
-
B.
Golian
Golian is a Slovak surname most notably associated with Ján Golian, a key military leader of the Slovak National Uprising during World War II.
-
C.
Ḍogrī
Ḍogrī is the native name of the Dogri language, an Indo-Aryan language spoken primarily in the Jammu region of India.
-
D.
Tyrnyauz
Tyrnyauz is a mountainous town in southwestern Russia known for its former tungsten-molybdenum mining industry and location in the North Caucasus.
-
E.
Shughni
Shughni is an Eastern Iranian language spoken primarily in the Badakhshan region of Tajikistan and Afghanistan, known for its use among the Shughni people in the Pamir Mountains.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe04918908190aad08defd1b26d97 |
completed | March 7, 2026, 8:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b03179d7448190bcdbea164856aaa2 |
completed | March 10, 2026, 2:58 p.m. |
Created at: March 6, 2026, 10:04 p.m.