Triple

T19363299
Position Surface form Disambiguated ID Type / Status
Subject Sikandra Rao E484333 entity
Predicate telephoneSystem P14970 FINISHED
Object Indian telephone numbering plan — NE NERFINISHED

How this triple was built (3 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: Indian telephone numbering plan | Statement: [Sikandra Rao, telephoneSystem, Indian telephone numbering plan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Indian telephone numbering plan
Context triple: [Sikandra Rao, telephoneSystem, Indian telephone numbering plan]
  • A. Russian telephone numbering plan
    The Russian telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Russia.
  • B. Israeli telephone numbering plan
    The Israeli telephone numbering plan is the national system that defines how phone numbers in Israel are structured, assigned, and dialed for local and international communication.
  • C. Japanese telephone numbering plan
    The Japanese telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Japan, including area codes, local numbers, and special service codes.
  • D. Philippine telephone numbering plan
    The Philippine telephone numbering plan is the national system that organizes and assigns area codes and phone numbers across the Philippines for landline and mobile telecommunications.
  • E. South African telephone numbering plan
    The South African telephone numbering plan is the national system that defines how phone numbers are structured, assigned, and dialed across South Africa’s regions and services.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Indian telephone numbering plan
Target entity description: The Indian telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed across India for landline and mobile services.
  • A. Russian telephone numbering plan
    The Russian telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Russia.
  • B. Israeli telephone numbering plan
    The Israeli telephone numbering plan is the national system that defines how phone numbers in Israel are structured, assigned, and dialed for local and international communication.
  • C. Japanese telephone numbering plan
    The Japanese telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Japan, including area codes, local numbers, and special service codes.
  • D. Philippine telephone numbering plan
    The Philippine telephone numbering plan is the national system that organizes and assigns area codes and phone numbers across the Philippines for landline and mobile telecommunications.
  • E. South African telephone numbering plan
    The South African telephone numbering plan is the national system that defines how phone numbers are structured, assigned, and dialed across South Africa’s regions and services.
  • F. None of above. chosen

Provenance (2 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619a897008190a2c62a50ca60de2d completed April 20, 2026, 12:18 p.m.
Created at: April 10, 2026, 1:34 p.m.