Triple

T29912903
Position Surface form Disambiguated ID Type / Status
Subject ITU-T G.781 E759716 entity
Predicate relatedTo P37 FINISHED
Object ITU-T G.813
ITU-T G.813 is an international telecommunications standard that specifies timing characteristics for SDH equipment clocks optimized for use in synchronous digital hierarchy networks.
 E1894311 NE 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: ITU-T G.813 | Statement: [ITU-T G.781, relatedTo, ITU-T G.813]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: ITU-T G.813
Triple: [ITU-T G.781, relatedTo, ITU-T G.813]
Generated description
ITU-T G.813 is an international telecommunications standard that specifies timing characteristics for SDH equipment clocks optimized for use in synchronous digital hierarchy networks.

Provenance (5 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_69f2246189fc8190996b63ee1f9a2374 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f6775b7e54819083176ce918b32eec completed May 2, 2026, 10:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2721e61e4c8190a2fac9483fcf7ea8 completed June 8, 2026, 8:11 p.m.
NEDg Description generation batch_6a2723c8705c819094334fcbfb95fa63 completed June 8, 2026, 8:19 p.m.
NED2 Entity disambiguation (via description) batch_6a2724cb1d48819088149a586c3c2ae6 completed June 8, 2026, 8:23 p.m.
Created at: April 29, 2026, 6:11 p.m.