Triple

T24418812
Position Surface form Disambiguated ID Type / Status
Subject National Route 9 (Vietnam) E615667 entity
Predicate historicallyUsedAsRouteTo P139623 FINISHED
Object Khe Sanh NE NERFINISHED

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: Khe Sanh | Statement: [National Route 9 (Vietnam), historicallyUsedAsRouteTo, Khe Sanh]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyUsedAsRouteTo
Context triple: [National Route 9 (Vietnam), historicallyUsedAsRouteTo, Khe Sanh]
  • A. usesFormerRouteOf
    Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
  • B. historicallyUsedFor
    Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
  • C. historicalRouteVia chosen
    Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
  • D. historicalRouteName
    Indicates that an entity has or is associated with a name it held historically as a route or pathway, distinct from its current official name.
  • E. nearHistoricalRoute
    Indicates that one entity is located close to a historically significant route or pathway.
  • 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_69e2d7e9bfac8190a748952a90957106 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f296a12a50819099fcdbc7096b53dd completed April 29, 2026, 11:39 p.m.
PD Predicate disambiguation batch_69f287cc4fd4819081e93cc638d9512d completed April 29, 2026, 10:35 p.m.
Created at: April 18, 2026, 2:13 a.m.