Triple

T36692363
Position Surface form Disambiguated ID Type / Status
Subject Usquert railway station E905991 entity
Predicate nearbySettlement P350 FINISHED
Object Usquert village
Usquert village is a small settlement in the province of Groningen in the northern Netherlands, known for its historic church mound and rural character.
E2193461 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: Usquert village | Statement: [Usquert railway station, nearbySettlement, Usquert village]
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: Usquert village
Triple: [Usquert railway station, nearbySettlement, Usquert village]
Generated description
Usquert village is a small settlement in the province of Groningen in the northern Netherlands, known for its historic church mound and rural character.

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_69f76e70d2448190bdd3ce781ba971c5 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c7e778a08190a9c943ce798902af completed May 3, 2026, 10:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a20e9b3908190befd8f94bf186286 completed June 23, 2026, 6 a.m.
NEDg Description generation batch_6a3a22e5e8fc8190a86afd5a2ceb8491 completed June 23, 2026, 6:08 a.m.
NED2 Entity disambiguation (via description) batch_6a3a233baf948190a8d3cfb019d6018a completed June 23, 2026, 6:10 a.m.
Created at: May 3, 2026, 4:12 p.m.