Triple

T983353
Position Surface form Disambiguated ID Type / Status
Subject Lappeenranta E21221 entity
Predicate distanceToRussianBorder_km P21939 FINISHED
Object about 30 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: about 30 | Statement: [Lappeenranta, distanceToRussianBorder_km, about 30]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceToRussianBorder_km
Context triple: [Lappeenranta, distanceToRussianBorder_km, about 30]
  • A. frontLineDistanceFromMoscow
    Indicates the measured distance between the current front line of a conflict and the city of Moscow.
  • B. distanceToBudapest_km
    Indicates the physical distance, measured in kilometers, between a given location and Budapest.
  • C. countryBorderProximity
    Indicates that one country is geographically close to or directly bordering another country.
  • D. distanceFromCapital
    Indicates the measured distance between a given location and the capital city of its corresponding region or country.
  • E. bordersToTheEast
    Indicates that one entity shares a boundary with another entity and is located directly to the east of it.
  • 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_69a493c383dc8190a03257f22d4b4183 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b493f5dc819090d239c2f7e083de completed March 1, 2026, 9:50 p.m.
PD Predicate disambiguation batch_69a4b2aa219081908a6b0ef786b4aa52 completed March 1, 2026, 9:42 p.m.
PDg Predicate description generation batch_69a4b345f890819092b51bf8128da461 completed March 1, 2026, 9:44 p.m.
Created at: March 1, 2026, 7:41 p.m.