Triple

T19311858
Position Surface form Disambiguated ID Type / Status
Subject Laos and Vietnam E482990 entity
Predicate haveBorderAgreements P59962 FINISHED
Object yes 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: yes | Statement: [Laos and Vietnam, haveBorderAgreements, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: haveBorderAgreements
Context triple: [Laos and Vietnam, haveBorderAgreements, yes]
  • A. haveCrossBorderAgreements chosen
    Indicates that there exist formal agreements or arrangements between entities that operate across national or jurisdictional borders.
  • B. hasBorderWithNonSovereignEntity
    Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
  • C. borderedBy
    Indicates that one entity shares a common boundary or edge with another entity.
  • D. hasBorderMeetingCountry
    Indicates that one country shares a land or maritime border with another country.
  • E. hasBorderWithinCountry
    Indicates that one region or area shares an internal boundary with another region or area within the same country.
  • 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604ce5de081909811c49f56ba94bb completed April 20, 2026, 10:49 a.m.
PD Predicate disambiguation batch_69e4dd0ef66881909d489d634eee817a completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:32 p.m.