Triple
T24385855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zator |
E614745
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object |
Market Square in Zator
Market Square in Zator is the town’s central historic plaza, serving as a focal point for local commerce, social life, and cultural events.
|
E1631919
|
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: Market Square in Zator | Statement: [Zator, hasLandmark, Market Square in Zator]
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: Market Square in Zator Triple: [Zator, hasLandmark, Market Square in Zator]
Generated description
Market Square in Zator is the town’s central historic plaza, serving as a focal point for local commerce, social life, and cultural events.
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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29454c36c8190b7820dbf5af7b695 |
completed | April 29, 2026, 11:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fd67e6b148190b1e3ffb6194b32fd |
completed | May 22, 2026, 4:07 a.m. |
| NEDg | Description generation | batch_6a0fd785e66c8190971031df082764bf |
completed | May 22, 2026, 4:11 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0fd83e09ac81909c039cdcf5e2d022 |
completed | May 22, 2026, 4:14 a.m. |
Created at: April 18, 2026, 2:03 a.m.