Triple

T19927261
Position Surface form Disambiguated ID Type / Status
Subject Didube E478956 entity
Predicate nativeName P15 FINISHED
Object დიდუბე NE NERFINISHED

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: დიდუბე | Statement: [Didube, nativeName, დიდუბე]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: დიდუბე
Context triple: [Didube, nativeName, დიდუბე]
  • A. Dorud
    Dorud is a city in western Iran’s Lorestan Province, known as a regional rail junction and gateway to the surrounding Zagros mountain landscapes.
  • B. Boyukdash
    Boyukdash is a prominent rocky hill in Azerbaijan’s Gobustan region, renowned for its ancient petroglyphs and archaeological remains that form part of the Gobustan Rock Art Cultural Landscape.
  • C. Doljo
    Doljo is a coastal barangay on Panglao Island in Bohol, Philippines, known for its white-sand beach and diving spots.
  • D. Didube chosen
    Didube is a metro station in Tbilisi, Georgia, serving as a key transit hub that connects the city’s metro system with major bus and marshrutka routes to other regions.
  • E. Durdar
    Durdar is a village near Carlisle in Cumbria, England, known for being the site of Carlisle Racecourse.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e521855c8190b41871700afc8d6a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e659ca52c881908dc8053bf61be4c4 completed April 20, 2026, 4:52 p.m.
Created at: April 10, 2026, 1:53 p.m.