Triple

T2799365
Position Surface form Disambiguated ID Type / Status
Subject Vanadzor E53114 entity
Predicate distanceFromYerevan_km P43261 FINISHED
Object approximately 120 LITERAL 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: approximately 120 | Statement: [Vanadzor, distanceFromYerevan_km, approximately 120]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceFromYerevan_km
Context triple: [Vanadzor, distanceFromYerevan_km, approximately 120]
  • A. distanceFrom Tbilisi
    Indicates the spatial distance between a given location or entity and the city of Tbilisi.
  • B. distanceFromAlmaty_km
    Indicates the distance, measured in kilometers, between a given place or object and the city of Almaty.
  • C. distanceFromBeirut
    Indicates the measured spatial distance between a given entity’s location and the city of Beirut.
  • D. distanceFromMoscow_km
    Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
  • E. distanceFromTelAviv_km
    Indicates the physical distance, measured in kilometers, between a given place and Tel Aviv.
  • F. None of above. chosen

Provenance (4 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_69ab495a90788190941b6917e1eca3a6 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abddf31eec8190a898713e53d1aa5c completed March 7, 2026, 8:12 a.m.
PD Predicate disambiguation batch_69abdd040f9481908e9c7a2df88ea1ae completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abddcc348081908b5f760899389d4f completed March 7, 2026, 8:11 a.m.
Created at: March 6, 2026, 9:58 p.m.