Triple

T26100499
Position Surface form Disambiguated ID Type / Status
Subject Mexican telephone numbering plan E658384 entity
Predicate nonGeographicServicesPrefix P148679 FINISHED
Object 900 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: 900 | Statement: [Mexican telephone numbering plan, nonGeographicServicesPrefix, 900]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nonGeographicServicesPrefix
Context triple: [Mexican telephone numbering plan, nonGeographicServicesPrefix, 900]
  • A. nonGeographicNumbersStartWith chosen
    Indicates that the identifiers assigned to non-geographic numbers begin with a specified leading sequence or prefix.
  • B. regionPrefix
    Indicates that one region’s identifier or code serves as the starting substring (prefix) of another region’s identifier or code, expressing a hierarchical or nested regional relationship.
  • C. addressPrefix
    Indicates that one address string serves as the starting portion or leading segment of another address.
  • D. namespacePrefix
    Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
  • E. nationalPrefixForDomesticCalls
    Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
  • 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_69ee5bc09c288190bc42a11972841383 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f6073a39408190994ac1c8983a7c0b completed May 2, 2026, 2:16 p.m.
PD Predicate disambiguation batch_69f5b0021da88190bdd4cf2698c23edf completed May 2, 2026, 8:04 a.m.
Created at: April 26, 2026, 7:54 p.m.