Triple

T571222
Position Surface form Disambiguated ID Type / Status
Subject Battle of Moscow E13666 entity
Predicate frontLineDistanceFromMoscow P16145 FINISHED
Object approximately 30 km at closest point 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 30 km at closest point | Statement: [Battle of Moscow, frontLineDistanceFromMoscow, approximately 30 km at closest point]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: frontLineDistanceFromMoscow
Context triple: [Battle of Moscow, frontLineDistanceFromMoscow, approximately 30 km at closest point]
  • A. otherMoscowAirport
    Indicates that one airport is another airport located in Moscow, distinguishing between multiple Moscow-area airports.
  • B. otherMajorMoscowAirports
    Indicates that the referenced airports are major airports serving Moscow other than the primary one under consideration.
  • C. distanceFromCapital
    Indicates the measured distance between a given location and the capital city of its corresponding region or country.
  • D. flightDistance
    Indicates the measured distance covered by a flight between its origin and destination.
  • E. distanceToBudapest_km
    Indicates the physical distance, measured in kilometers, between a given location and Budapest.
  • 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_69a4933fa4d88190a7949cc83c08c5c1 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b483ac08190b3be152a7cf42011 completed March 1, 2026, 8:02 p.m.
PD Predicate disambiguation batch_69a494c2caac819086ab316fa49d324c completed March 1, 2026, 7:34 p.m.
PDg Predicate description generation batch_69a498dd579081908e02368a4c5efc8c completed March 1, 2026, 7:51 p.m.
Created at: March 1, 2026, 7:33 p.m.