Triple

T28582947

Position	Surface form	Disambiguated ID	Type / Status
Subject	6LoWPAN	`E723424`	entity
Predicate	specifiedIn	`P775`	FINISHED
Object	RFC 8025 RFC 8025 is an IETF standards document that defines aspects of IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN), focusing on efficient communication in constrained IoT environments.	`E1825100`	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 8025 | Statement: [6LoWPAN, specifiedIn, RFC 8025]

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 8025
Triple: [6LoWPAN, specifiedIn, RFC 8025]

Generated description

RFC 8025 is an IETF standards document that defines aspects of IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN), focusing on efficient communication in constrained IoT environments.

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_69f01d7f92e481909847f5f3f3174a89`	completed	April 28, 2026, 2:37 a.m.
NER	Named-entity recognition	`batch_69f650cd6ee08190a5c05f83e4b95896`	completed	May 2, 2026, 7:30 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a1cb6f458a48190b375e96f42364f1c`	completed	May 31, 2026, 10:32 p.m.
NEDg	Description generation	`batch_6a1cba6242d88190b72a23553705c221`	completed	May 31, 2026, 10:46 p.m.
NED2	Entity disambiguation (via description)	`batch_6a1cbae69fcc819089e092d9f9a0e0ba`	completed	May 31, 2026, 10:49 p.m.

Created at: April 28, 2026, 4:16 a.m.