Triple

T38459659
Position Surface form Disambiguated ID Type / Status
Subject Cristuru Secuiesc E912414 entity
Predicate hasEthnicRegion P72539 FINISHED
Object Székely region
The Székely region is a historic, predominantly Hungarian-inhabited area in eastern Transylvania, Romania, known for its distinct Székely cultural and linguistic identity.
E2276889 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: Székely region | Statement: [Cristuru Secuiesc, hasEthnicRegion, Székely region]
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: Székely region
Triple: [Cristuru Secuiesc, hasEthnicRegion, Székely region]
Generated description
The Székely region is a historic, predominantly Hungarian-inhabited area in eastern Transylvania, Romania, known for its distinct Székely cultural and linguistic identity.

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_69f76e84e2dc81908badf05b3aafa9ea completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcce05c6608190b2a8a2a15740a3bf completed May 7, 2026, 5:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41ea7d91a08190bd73a9b76bdc293f completed June 29, 2026, 3:46 a.m.
NEDg Description generation batch_6a41ebfa7c488190b5447ad0e2dafa3a completed June 29, 2026, 3:52 a.m.
NED2 Entity disambiguation (via description) batch_6a41ed04b20c81908453356ba5af16ee completed June 29, 2026, 3:56 a.m.
Created at: May 3, 2026, 4:31 p.m.