Triple

T37682772
Position Surface form Disambiguated ID Type / Status
Subject Magyar tribal confederation E938281 entity
Predicate includedTribe P32607 FINISHED
Object Keszi tribe
The Keszi tribe was one of the constituent Hungarian (Magyar) tribes that formed part of the early medieval Magyar tribal alliance in the Carpathian Basin.
E2251239 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: Keszi tribe | Statement: [Magyar tribal confederation, includedTribe, Keszi tribe]
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: Keszi tribe
Triple: [Magyar tribal confederation, includedTribe, Keszi tribe]
Generated description
The Keszi tribe was one of the constituent Hungarian (Magyar) tribes that formed part of the early medieval Magyar tribal alliance in the Carpathian Basin.

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_69f76ed881408190bc62a969530a4a53 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbadfa55448190a56d97596ff29dc5 completed May 6, 2026, 9:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a412c9742e881908513ac0918f2eae8 completed June 28, 2026, 2:15 p.m.
NEDg Description generation batch_6a41339400a0819095b8d72e742216bb completed June 28, 2026, 2:45 p.m.
NED2 Entity disambiguation (via description) batch_6a41352aedc4819084253d0f99a12684 completed June 28, 2026, 2:52 p.m.
Created at: May 3, 2026, 4:18 p.m.