Triple
T2877737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lübeck |
E56916
|
entity |
| Predicate | twinCity |
P1072
|
FINISHED |
| Object | Włocławek |
E338414
|
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: Włocławek | Statement: [Lübeck, twinCity, Włocławek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Włocławek Context triple: [Lübeck, twinCity, Włocławek]
-
A.
Włocławek
chosen
Włocławek is a historic city in north-central Poland on the Vistula River, known for its medieval heritage and role as a regional industrial and cultural center.
-
B.
Łowicz
Łowicz is a historic town in central Poland known for its rich folk traditions, distinctive regional costumes, and baroque architecture.
-
C.
Inowrocław
Inowrocław is a historic spa and industrial city in north-central Poland, known for its saltworks and location in the Kuyavia region.
-
D.
Glogów
Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
-
E.
Opole
Opole is a historic city in southwestern Poland, known as one of the country’s oldest urban centers and a regional cultural hub.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe007329c8190b0bc1851c7307124 |
completed | March 7, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bee04d0b0c81908876ff0d675b93ae |
completed | March 21, 2026, 6:15 p.m. |
Created at: March 6, 2026, 10:03 p.m.