Triple

T38378367
Position Surface form Disambiguated ID Type / Status
Subject Greater Afghanistan E893687 entity
Predicate implicatesBorderDispute P62867 FINISHED
Object Afghanistan–Pakistan border 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: Afghanistan–Pakistan border | Statement: [Greater Afghanistan, implicatesBorderDispute, Afghanistan–Pakistan border]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: implicatesBorderDispute
Context triple: [Greater Afghanistan, implicatesBorderDispute, Afghanistan–Pakistan border]
  • A. borderDisputesWith
    Indicates that there are contested or unresolved boundary claims between two entities.
  • B. associatedTerritoryDispute chosen
    Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
  • C. borderDisputeResolvedBy
    Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
  • D. hasDisputedMaritimeBoundary
    Indicates that there is an unresolved or contested maritime boundary claim between two or more entities.
  • E. locatedInDisputedTerritory
    Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
  • 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_69f76e4b1f748190a380696a16eae4a2 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcd313e61c8190b174b331365b803f completed May 7, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69fcd1f6b2e08190bf0300ae7c9ae67a completed May 7, 2026, 5:55 p.m.
Created at: May 3, 2026, 4:31 p.m.