Triple

T14988532
Position Surface form Disambiguated ID Type / Status
Subject Paraćin E373768 entity
Predicate distanceFromBelgrade_km P63607 FINISHED
Object approximately 160 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 160 | Statement: [Paraćin, distanceFromBelgrade_km, approximately 160]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceFromBelgrade_km
Context triple: [Paraćin, distanceFromBelgrade_km, approximately 160]
  • A. distanceToBelgrade chosen
    Indicates the spatial distance between a given entity and the city of Belgrade.
  • B. distanceToTirana_km
    Indicates the physical distance, measured in kilometers, between a given place and the city of Tirana.
  • C. distanceToBudapest_km
    Indicates the physical distance, measured in kilometers, between a given location and Budapest.
  • D. distanceFromBratislava_km
    Indicates the distance, measured in kilometers, between a given entity’s location and the city of Bratislava.
  • E. distanceToSubotica
    Indicates the measured distance between a given entity’s location and the city of Subotica.
  • F. None of above.

Provenance (3 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_69d85ccc84388190aa151e5173370c8d completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7148a308190a687f4d0d61397c6 completed April 15, 2026, 12:08 a.m.
PD Predicate disambiguation batch_69de9a6169b48190a679609febd2d0e3 completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:53 a.m.