Triple
T4950057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabasaran |
E111145
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object |
Rutul
Rutul is a Northeast Caucasian language spoken by the Rutul people primarily in southern Dagestan, Russia, and parts of northern Azerbaijan.
|
E483554
|
NE FINISHED |
How this triple was built (4 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: Rutul | Statement: [Tabasaran, closelyRelatedTo, Rutul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rutul Context triple: [Tabasaran, closelyRelatedTo, Rutul]
-
A.
Otradnoye
Otradnoye is a town in Russia located within the Leningrad (Saint Petersburg) region, known for its position along the Neva River and proximity to Saint Petersburg.
-
B.
Otradnoye
Otradnoye is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Otradnoye District in northern Moscow.
-
C.
Kudrovo
Kudrovo is a rapidly growing suburban town on the eastern outskirts of Saint Petersburg, Russia, known for its dense residential developments and proximity to the city.
-
D.
Terekhovo
Terekhovo is a metro station on Moscow’s Big Circle Line, serving the Terekhovo area in the western part of the city.
-
E.
Oreshek
Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Rutul Triple: [Tabasaran, closelyRelatedTo, Rutul]
Generated description
Rutul is a Northeast Caucasian language spoken by the Rutul people primarily in southern Dagestan, Russia, and parts of northern Azerbaijan.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rutul Target entity description: Rutul is a Northeast Caucasian language spoken by the Rutul people primarily in southern Dagestan, Russia, and parts of northern Azerbaijan.
-
A.
Otradnoye
Otradnoye is a town in Russia located within the Leningrad (Saint Petersburg) region, known for its position along the Neva River and proximity to Saint Petersburg.
-
B.
Otradnoye
Otradnoye is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Otradnoye District in northern Moscow.
-
C.
Kudrovo
Kudrovo is a rapidly growing suburban town on the eastern outskirts of Saint Petersburg, Russia, known for its dense residential developments and proximity to the city.
-
D.
Terekhovo
Terekhovo is a metro station on Moscow’s Big Circle Line, serving the Terekhovo area in the western part of the city.
-
E.
Oreshek
Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
- F. None of above. chosen
Provenance (5 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7167f97481908db5bfa9338e3824 |
completed | March 20, 2026, 4:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81d03b088190aa6601298ee4d8fd |
completed | March 21, 2026, 11:32 a.m. |
| NEDg | Description generation | batch_69be8625c100819086b9621b43268164 |
completed | March 21, 2026, 11:51 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69be8675c7e08190b01880a679554412 |
completed | March 21, 2026, 11:52 a.m. |
Created at: March 20, 2026, 1:31 p.m.