Triple

T19927224
Position Surface form Disambiguated ID Type / Status
Subject Avlabari E478955 entity
Predicate connectsToDistrict P45423 FINISHED
Object Avlabari 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: Avlabari | Statement: [Avlabari, connectsToDistrict, Avlabari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Avlabari
Context triple: [Avlabari, connectsToDistrict, Avlabari]
  • A. Avlabari chosen
    Avlabari is a metro station in Tbilisi, Georgia, serving the historic Avlabari district on the city's left bank.
  • B. Gardabani
    Gardabani is a town in southeastern Georgia known for its role as an industrial and energy hub within the Kvemo Kartli region.
  • C. Oreshak
    Oreshak is a village in central Bulgaria known for its proximity to the historic Troyan Monastery and its traditional crafts and cultural heritage.
  • D. Paravani
    Paravani is a mythological peacock that serves as the divine mount (vahana) of the Hindu war god Kartikeya.
  • E. Paravani
    Paravani is a river in southern Georgia that flows from the volcanic Javakheti Plateau into the Kura River basin.
  • 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.