Triple

T7492400
Position Surface form Disambiguated ID Type / Status
Subject Public Switched Telephone Network E177035 entity
Predicate usesNumberingPlan P53890 FINISHED
Object E.164 international numbering plan 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: E.164 international numbering plan | Statement: [Public Switched Telephone Network, usesNumberingPlan, E.164 international numbering plan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesNumberingPlan
Context triple: [Public Switched Telephone Network, usesNumberingPlan, E.164 international numbering plan]
  • A. telephoneNumberingPlan chosen
    Indicates a relationship where a telephone numbering plan defines or governs how telephone numbers are structured, assigned, or managed for a given telecommunication context.
  • B. serviceNumbering
    Indicates that a specific service is assigned or associated with a particular identifying number or code.
  • C. callingCodeType
    Indicates the type or category of a telephone calling code associated with an entity.
  • D. callingCode
    Indicates the telephone country or area code associated with an entity for making phone calls.
  • E. supportsNumberPorting
    Indicates that an entity enables or allows the transfer of an existing phone number from one service or provider to another.
  • 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_69c69f2583808190bd1a4936c42a5815 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f81b431481908214b69c6c8d83bc completed March 27, 2026, 9:35 p.m.
PD Predicate disambiguation batch_69c6f4d266d88190982cf5d2ee2e9564 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:43 p.m.