Triple

T29389032

Position	Surface form	Disambiguated ID	Type / Status
Subject	RFC 8010	`E745326`	entity
Predicate	obsoletes	`P101`	FINISHED
Object	RFC 3399 RFC 3399 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of Internet printing protocols before later being superseded by RFC 8010.	`E1911436`	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: RFC 3399 | Statement: [RFC 8010, obsoletes, RFC 3399]

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: RFC 3399
Triple: [RFC 8010, obsoletes, RFC 3399]

Generated description

RFC 3399 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of Internet printing protocols before later being superseded by RFC 8010.

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_69f0a79dfabc81908755382ee47791e2`	completed	April 28, 2026, 12:27 p.m.
NER	Named-entity recognition	`batch_69f669d578608190962d35116a01420c`	completed	May 2, 2026, 9:17 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a277bf1b158819089ccf7b70366b27e`	completed	June 9, 2026, 2:35 a.m.
NEDg	Description generation	`batch_6a277fe105cc8190bd2b4b0811107107`	completed	June 9, 2026, 2:52 a.m.
NED2	Entity disambiguation (via description)	`batch_6a2780aa64b88190a2aa299bf7c7bca3`	completed	June 9, 2026, 2:55 a.m.

Created at: April 28, 2026, 2:41 p.m.