Triple

T22331513
Position Surface form Disambiguated ID Type / Status
Subject Telecommunication Management Network E552033 entity
Predicate definedIn P775 FINISHED
Object ITU-T Recommendation M.3010 — 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: ITU-T Recommendation M.3010 | Statement: [Telecommunication Management Network, definedIn, ITU-T Recommendation M.3010]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: ITU-T Recommendation M.3010
Context triple: [Telecommunication Management Network, definedIn, ITU-T Recommendation M.3010]
  • A. ITU-T Recommendation Q.1901
    ITU-T Recommendation Q.1901 is an international telecommunications standard that defines the Bearer Independent Call Control (BICC) protocol for call control over diverse transport networks.
  • B. ITU-T Recommendation Q.1902
    ITU-T Recommendation Q.1902 is an international telecommunications standard that defines the Bearer Independent Call Control (BICC) protocol for call control in next-generation networks.
  • C. ITU-T Recommendation G.8263
    ITU-T Recommendation G.8263 is an international standard that specifies timing and synchronization requirements for packet-based networks, particularly for frequency synchronization over packet-switched infrastructures.
  • D. ITU-R M.1036
    ITU-R M.1036 is an ITU Radiocommunication Sector recommendation that defines frequency arrangements and channel plans for terrestrial IMT (mobile broadband) systems across various radio bands.
  • E. ITU-R M.1371
    ITU-R M.1371 is an International Telecommunication Union recommendation that specifies the technical standards and protocols for the Automatic Identification System (AIS) used in maritime navigation and vessel tracking.
  • 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: ITU-T Recommendation M.3010
Target entity description: ITU-T Recommendation M.3010 is an international standard that specifies the architectural framework and principles for managing telecommunication networks and services.
  • A. ITU-T Recommendation Q.1901
    ITU-T Recommendation Q.1901 is an international telecommunications standard that defines the Bearer Independent Call Control (BICC) protocol for call control over diverse transport networks.
  • B. ITU-T Recommendation Q.1902
    ITU-T Recommendation Q.1902 is an international telecommunications standard that defines the Bearer Independent Call Control (BICC) protocol for call control in next-generation networks.
  • C. ITU-T Recommendation G.8263
    ITU-T Recommendation G.8263 is an international standard that specifies timing and synchronization requirements for packet-based networks, particularly for frequency synchronization over packet-switched infrastructures.
  • D. ITU-R M.1036
    ITU-R M.1036 is an ITU Radiocommunication Sector recommendation that defines frequency arrangements and channel plans for terrestrial IMT (mobile broadband) systems across various radio bands.
  • E. ITU-R M.1371
    ITU-R M.1371 is an International Telecommunication Union recommendation that specifies the technical standards and protocols for the Automatic Identification System (AIS) used in maritime navigation and vessel tracking.
  • 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_69e11e482f788190b78d1588fc26d606 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1577b555c8190ac61c026ee7dfb2b completed April 29, 2026, 12:57 a.m.
Created at: April 16, 2026, 8:43 p.m.