Triple

T25162450
Position Surface form Disambiguated ID Type / Status
Subject Argentina and Chile E626476 entity
Predicate shareBorderAgreement P166114 FINISHED
Object Boundary Treaty of 1881 between Argentina and Chile 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: Boundary Treaty of 1881 between Argentina and Chile | Statement: [Argentina and Chile, shareBorderAgreement, Boundary Treaty of 1881 between Argentina and Chile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareBorderAgreement
Context triple: [Argentina and Chile, shareBorderAgreement, Boundary Treaty of 1881 between Argentina and Chile]
  • A. shareNotableBorderRegion
    Indicates that two entities share a common border in a region that is particularly significant or notable (e.g., historically, politically, or geographically).
  • B. shareBorderLengthApprox
    Indicates that two entities share a common boundary whose length is approximately equal to a specified value.
  • C. sharesBorderingNetworkWith
    Indicates that two entities are connected through adjacent or directly neighboring positions within the same network structure.
  • D. relatedBorder
    Indicates that two geographic or political entities share a common boundary or border with each other.
  • E. sharesBorderType
    Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
  • 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_69e2ff2834ec8190b0872e2ec3d76023 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f66003a3f48190a2ba6da5aafbb5cb completed May 2, 2026, 8:35 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
PDg Predicate description generation batch_69f65f75ac608190a62cd6afce14f68e completed May 2, 2026, 8:32 p.m.
Created at: April 18, 2026, 6:31 a.m.