Triple

T24416864
Position Surface form Disambiguated ID Type / Status
Subject President of UEFA E615606 entity
Predicate seatOfOffice P761 FINISHED
Object UEFA headquarters
UEFA headquarters is the central administrative and decision-making center of European football’s governing body, located in Nyon, Switzerland.
E1634741 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: UEFA headquarters | Statement: [President of UEFA, seatOfOffice, UEFA headquarters]
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: UEFA headquarters
Triple: [President of UEFA, seatOfOffice, UEFA headquarters]
Generated description
UEFA headquarters is the central administrative and decision-making center of European football’s governing body, located in Nyon, Switzerland.

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_69e2d7e9bfac8190a748952a90957106 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2958645248190a22bd0b8bcc2dfe2 completed April 29, 2026, 11:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fe36849a0819098ee2d49abcda1ea completed May 22, 2026, 5:02 a.m.
NEDg Description generation batch_6a0fe4bfcea881909cf308d946a88c4c completed May 22, 2026, 5:08 a.m.
NED2 Entity disambiguation (via description) batch_6a0fe54cbdac8190b45d5570023762c4 completed May 22, 2026, 5:10 a.m.
Created at: April 18, 2026, 2:13 a.m.