Triple

T2440388
Position Surface form Disambiguated ID Type / Status
Subject Khyber Pass E53258 entity
Predicate controlledHistoricallyBy P5058 FINISHED
Object local Pashtun tribes 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: local Pashtun tribes | Statement: [Khyber Pass, controlledHistoricallyBy, local Pashtun tribes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controlledHistoricallyBy
Context triple: [Khyber Pass, controlledHistoricallyBy, local Pashtun tribes]
  • A. historicallyControlledBy chosen
    Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
  • B. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • C. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • D. historicallyExtendedBy
    Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
  • E. historicallyGivenIn
    Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
  • 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_69ab495b6dac8190ac82661aa1452222 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abcebf7cac8190889e6890d72c256c completed March 7, 2026, 7:07 a.m.
PD Predicate disambiguation batch_69abc5ac11b081908ce6a506e81a742a completed March 7, 2026, 6:29 a.m.
Created at: March 6, 2026, 9:43 p.m.