Triple

T27572707
Position Surface form Disambiguated ID Type / Status
Subject CLNS E696075 entity
Predicate fullName P16 FINISHED
Object Connectionless Network Service
Connectionless Network Service is a network-layer protocol defined by the OSI model that provides datagram-based, connectionless communication similar to IP.
E1778228 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: Connectionless Network Service | Statement: [CLNS, fullName, Connectionless Network Service]
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: Connectionless Network Service
Triple: [CLNS, fullName, Connectionless Network Service]
Generated description
Connectionless Network Service is a network-layer protocol defined by the OSI model that provides datagram-based, connectionless communication similar to IP.

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_69ef53891af88190a193c5e2a1dac9b1 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62fed98888190bdc01137b65acbb6 completed May 2, 2026, 5:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12c5d4b98881908b3a709f933ba943 completed May 24, 2026, 9:33 a.m.
NEDg Description generation batch_6a12c73b99948190b0b9b9fc080317bb completed May 24, 2026, 9:39 a.m.
NED2 Entity disambiguation (via description) batch_6a12c7b518a88190af3af56ac1ba03dd completed May 24, 2026, 9:41 a.m.
Created at: April 27, 2026, 1:44 p.m.