Triple

T29794830

Position	Surface form	Disambiguated ID	Type / Status
Subject	GNSO	`E756516`	entity
Predicate	hasStakeholderGroup	`P26016`	FINISHED
Object	Contracted Parties House The Contracted Parties House is the ICANN GNSO voting bloc that represents domain name registries and registrars in policy development processes.	`E1883814`	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: Contracted Parties House | Statement: [GNSO, hasStakeholderGroup, Contracted Parties House]

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: Contracted Parties House
Triple: [GNSO, hasStakeholderGroup, Contracted Parties House]

Generated description

The Contracted Parties House is the ICANN GNSO voting bloc that represents domain name registries and registrars in policy development processes.

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_69f22454583081908927516cb9938d1d`	completed	April 29, 2026, 3:31 p.m.
NER	Named-entity recognition	`batch_69f674e5cf0c81908f779723cf602daf`	completed	May 2, 2026, 10:04 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a26c90a7bac8190a9c0317842364d01`	completed	June 8, 2026, 1:52 p.m.
NEDg	Description generation	`batch_6a26d44f8184819089648aaf5fea3616`	completed	June 8, 2026, 2:40 p.m.
NED2	Entity disambiguation (via description)	`batch_6a26d50e86a08190a4d70c2b0168a145`	completed	June 8, 2026, 2:43 p.m.

Created at: April 29, 2026, 5:14 p.m.