Triple

T33922113
Position Surface form Disambiguated ID Type / Status
Subject Thống Nhất line E869641 entity
Predicate isMainCorridor P179729 FINISHED
Object north–south railway corridor of Vietnam 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: north–south railway corridor of Vietnam | Statement: [Thống Nhất line, isMainCorridor, north–south railway corridor of Vietnam]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMainCorridor
Context triple: [Thống Nhất line, isMainCorridor, north–south railway corridor of Vietnam]
  • A. otherMainCorridor
    Indicates that one corridor is an alternative or secondary main corridor relative to another within the same structure or network.
  • B. hasCorridor
    Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
  • C. isMostHeavilyTraveledCorridorIn
    Indicates that a particular route or corridor experiences the highest volume of travel or traffic within a specified area or region.
  • D. inCorridor
    Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
  • E. isPartOfCorridorSystem
    Indicates that one entity forms a component or segment within a larger interconnected corridor system.
  • 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_69f349992c508190aa4afa24a086cc8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f727bde8f88190ad746ca515134ca1 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72739c30c81908642eef3feb3afcf completed May 3, 2026, 10:45 a.m.
PDg Predicate description generation batch_69f727bd39b081908457590c3ba9b745 completed May 3, 2026, 10:47 a.m.
Created at: May 1, 2026, 1:49 a.m.