Triple
T9857387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expressway S17 |
E239620
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Piaski |
E825705
|
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: Piaski | Statement: [Expressway S17, passesNear, Piaski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piaski Context triple: [Expressway S17, passesNear, Piaski]
-
A.
Piaski
Piaski is a small Polish coastal village situated on the Vistula Spit near the border with Russia’s Kaliningrad Oblast.
-
B.
Piaski
chosen
Piaski is a town in eastern Poland that serves as a local transport hub and junction point for regional roads and expressways.
-
C.
Biała Piska
Biała Piska is a small town in northeastern Poland known for its location amid the lakes and forests of the Warmian-Masurian region.
-
D.
Rakoń
Rakoń is a mountain peak in the Western Tatras on the Polish-Slovak border, popular with hikers for its scenic ridge views.
-
E.
Łeba
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb39864188190a2d8c0ee911f00c2 |
completed | April 2, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1ead91ee88190bd4cb28ab16bf703 |
completed | April 5, 2026, 4:53 a.m. |
Created at: March 30, 2026, 8:35 p.m.