Triple

T25115192
Position Surface form Disambiguated ID Type / Status
Subject Lodhran–Khanewal via Jahanian Line E629107 entity
Predicate linkRole P157658 FINISHED
Object connects Lodhran with Khanewal via Jahanian 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: connects Lodhran with Khanewal via Jahanian | Statement: [Lodhran–Khanewal via Jahanian Line, linkRole, connects Lodhran with Khanewal via Jahanian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: linkRole
Context triple: [Lodhran–Khanewal via Jahanian Line, linkRole, connects Lodhran with Khanewal via Jahanian]
  • A. linkType
    Indicates the specific kind or category of relationship that connects two linked entities.
  • B. anchorRole
    Indicates that one entity serves as a primary or reference role to which other related roles or elements are connected or aligned.
  • C. linkTypeKey
    Indicates the specific type or category of link that characterizes the relationship between two entities.
  • D. linkedLocation
    Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
  • E. linkedSupport
    Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
  • 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_69e2ff3169d08190973b6061d5009abd completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f465c66cc48190b66b14e4b9036432 completed May 1, 2026, 8:35 a.m.
PD Predicate disambiguation batch_69f442c861188190967655c6d8012380 completed May 1, 2026, 6:06 a.m.
PDg Predicate description generation batch_69f448fe11f08190bdd53ca7ba2d51e4 completed May 1, 2026, 6:32 a.m.
Created at: April 18, 2026, 6:27 a.m.