Triple

T23834827
Position Surface form Disambiguated ID Type / Status
Subject Dyskobolia Grodzisk Wielkopolski E590819 entity
Predicate basedIn P40 FINISHED
Object Grodzisk Wielkopolski
Grodzisk Wielkopolski is a town in western Poland’s Greater Poland Voivodeship, known for its local industry and football tradition.
E1977174 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: Grodzisk Wielkopolski | Statement: [Dyskobolia Grodzisk Wielkopolski, basedIn, Grodzisk Wielkopolski]
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: Grodzisk Wielkopolski
Triple: [Dyskobolia Grodzisk Wielkopolski, basedIn, Grodzisk Wielkopolski]
Generated description
Grodzisk Wielkopolski is a town in western Poland’s Greater Poland Voivodeship, known for its local industry and football tradition.

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_69e25d1de32c8190a907afe9c3d6cd6d completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c7f9eaa081909531f1322e0ec9ca completed April 29, 2026, 8:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2d9d24465c8190abc91eefc8271da9 completed June 13, 2026, 6:10 p.m.
NEDg Description generation batch_6a2d9e2593f4819092c89187e84af3c9 completed June 13, 2026, 6:15 p.m.
NED2 Entity disambiguation (via description) batch_6a2d9f083f0481909184bb37c1ce0e7a completed June 13, 2026, 6:18 p.m.
Created at: April 17, 2026, 8:07 p.m.