Triple

T8670114
Position Surface form Disambiguated ID Type / Status
Subject Al-Hinakiya E205772 entity
Predicate telephoneCallingCodeOfCountry P247 FINISHED
Object +966 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: +966 | Statement: [Al-Hinakiya, telephoneCallingCodeOfCountry, +966]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: telephoneCallingCodeOfCountry
Context triple: [Al-Hinakiya, telephoneCallingCodeOfCountry, +966]
  • A. callingCode chosen
    Indicates the telephone country or area code associated with an entity for making phone calls.
  • B. callingCodeType
    Indicates the type or category of a telephone calling code associated with an entity.
  • C. UICCountryCode
    Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
  • D. countryCodePart
    Indicates that one entity is a segment or component of a standardized country code associated with another entity.
  • E. countryCodeFormat
    Indicates the standardized structure or pattern in which a country's code must be represented.
  • 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_69ca83516ae88190aefe034b3bc589e3 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc4917cb9881909a73b74e54250613 completed March 31, 2026, 10:22 p.m.
PD Predicate disambiguation batch_69cc4564e018819081036722f3e42a71 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:31 p.m.