Triple

T27612645
Position Surface form Disambiguated ID Type / Status
Subject IETF governance E700365 entity
Predicate documentedIn P309 FINISHED
Object BCP 79
BCP 79 is an IETF Best Current Practice document that defines the organization’s policies and procedures for handling intellectual property rights in the standards process.
 E1784044 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: BCP 79 | Statement: [IETF governance, documentedIn, BCP 79]
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: BCP 79
Triple: [IETF governance, documentedIn, BCP 79]
Generated description
BCP 79 is an IETF Best Current Practice document that defines the organization’s policies and procedures for handling intellectual property rights in the standards process.

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_69ef6a4f1d9c8190b0705acda054368d completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f630a10e808190baf5d28151c1063e completed May 2, 2026, 5:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12da8486888190b3c228233b90facb completed May 24, 2026, 11:01 a.m.
NEDg Description generation batch_6a12db2833688190af921e97c6e5d05d completed May 24, 2026, 11:04 a.m.
NED2 Entity disambiguation (via description) batch_6a12db977df48190b71bce8408b51269 completed May 24, 2026, 11:05 a.m.
Created at: April 27, 2026, 2:11 p.m.