Triple

T24780786
Position Surface form Disambiguated ID Type / Status
Subject Schinnen (former municipality) E619989 entity
Predicate borderedBy P224 FINISHED
Object Beek (Limburg)
Beek (Limburg) is a town and municipality in the Dutch province of Limburg, known for its historical village center and proximity to Maastricht and major transport routes.
E1654095 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: Beek (Limburg) | Statement: [Schinnen (former municipality), borderedBy, Beek (Limburg)]
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: Beek (Limburg)
Triple: [Schinnen (former municipality), borderedBy, Beek (Limburg)]
Generated description
Beek (Limburg) is a town and municipality in the Dutch province of Limburg, known for its historical village center and proximity to Maastricht and major transport routes.

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_69e2fabdbe8c8190adbb9434b8636cad completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f410d67a208190909034a085b20b59 completed May 1, 2026, 2:32 a.m.
NED1 Entity disambiguation (via context triple) batch_6a101c2148888190a27769b761ea2154 completed May 22, 2026, 9:04 a.m.
NEDg Description generation batch_6a1028676c7081909fc47b255611307a completed May 22, 2026, 9:56 a.m.
NED2 Entity disambiguation (via description) batch_6a10294485508190a91d9ec391181047 completed May 22, 2026, 10 a.m.
Created at: April 18, 2026, 4:44 a.m.