Triple

T13415455
Position Surface form Disambiguated ID Type / Status
Subject Faridkot E313199 entity
Predicate telecomCircle P109818 FINISHED
Object Punjab telecom circle 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: Punjab telecom circle | Statement: [Faridkot, telecomCircle, Punjab telecom circle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: telecomCircle
Context triple: [Faridkot, telecomCircle, Punjab telecom circle]
  • A. telecommunicationsProvider
    Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
  • B. telecommunicationSystem
    Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
  • C. countryNetwork
    Indicates a relationship where countries are connected or associated through some form of shared system, collaboration, or interaction.
  • D. radioTelephonyDesignatorFor
    Indicates that one entity is the assigned radiotelephony (spoken) call sign or designator used in radio communications for another entity.
  • E. networkOperatorMCC_MNC
    Indicates that a specific mobile network operator is identified by the given combination of Mobile Country Code (MCC) and Mobile Network Code (MNC).
  • 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_69d806ad0c44819088833ae1ec9e9690 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaeb6e904819098cc9153fd2feaf5 completed April 12, 2026, 2:39 p.m.
PD Predicate disambiguation batch_69d9a0355de48190bb3fb96912e20df3 completed April 11, 2026, 1:13 a.m.
PDg Predicate description generation batch_69dadcce5a808190847f2a7833b67a5a completed April 11, 2026, 11:44 p.m.
Created at: April 9, 2026, 9:39 p.m.