Triple

T18293234
Position Surface form Disambiguated ID Type / Status
Subject Series G E438166 entity
Predicate includesRecommendation P58814 FINISHED
Object G.9960 NE NERFINISHED

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: G.9960 | Statement: [Series G, includesRecommendation, G.9960]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: G.9960
Context triple: [Series G, includesRecommendation, G.9960]
  • A. G.9960 chosen
    G.9960 is an ITU-T telecommunications standard that defines the physical layer for high-speed data transmission over power lines, coaxial cables, and phone lines, commonly known as G.hn.
  • B. G.9961
    G.9961 is an ITU-T standard that defines the data link layer (including management and control functions) for G.hn home networking over existing wiring such as power lines, phone lines, and coaxial cables.
  • C. G.9701
    G.9701 is an ITU-T standard that defines the physical layer specifications for G.fast broadband access over existing copper telephone lines.
  • D. G.196
    G.196 is an ITU-T standard that defines characteristics and requirements for digital speech and audio coding systems within telecommunications networks.
  • E. G.826x
    G.826x is an ITU-T standards series that defines methods and requirements for packet-based frequency and time synchronization in telecommunications networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50100d6488190bbe73668df9c4046 completed April 19, 2026, 4:21 p.m.
Created at: April 10, 2026, 10:35 a.m.