Triple

T28193762
Position Surface form Disambiguated ID Type / Status
Subject Seoul–Busan E716382 entity
Predicate approximateRailDistanceKm P65643 FINISHED
Object about 410 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 410 | Statement: [Seoul–Busan, approximateRailDistanceKm, about 410]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateRailDistanceKm
Context triple: [Seoul–Busan, approximateRailDistanceKm, about 410]
  • A. approximateDistanceKm
    Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
  • B. distanceToByRail chosen
    Indicates the distance between two locations when traveling via railway routes.
  • C. approximateRouteLength
    Indicates the estimated total distance or length of a given route, rather than its exact measured value.
  • D. tourDistanceApproxKm
    Indicates an approximate total distance, measured in kilometers, covered during a tour or journey.
  • E. depthApproxKm
    Indicates the approximate depth of something measured in kilometers.
  • 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_69efd6b612f48190a72012b520afbd10 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
Created at: April 27, 2026, 10:26 p.m.