Triple
T1985506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tartu |
E43129
|
entity |
| Predicate | twinnedWith |
P1072
|
FINISHED |
| Object | Płock |
E229370
|
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: Płock | Statement: [Tartu, twinnedWith, Płock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Płock Context triple: [Tartu, twinnedWith, Płock]
-
A.
Płock
chosen
Płock is a historic city in central Poland known for its medieval architecture and scenic location on the banks of the Vistula River.
-
B.
Siedlce
Siedlce is a city in eastern Poland known as a local economic, cultural, and transportation hub.
-
C.
Radom
Radom is a city in central Poland known as an important regional industrial and cultural center.
-
D.
Ostrołęka
Ostrołęka is a town in east-central Poland known for its historical role in the Napoleonic Wars and as a local industrial and administrative center.
-
E.
Olsztyn
Olsztyn is a historic city in northern Poland known for its medieval architecture, lakes, and role as the capital of the Warmian-Masurian Voivodeship.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb821c2d48190abea6c89f37b51b1 |
completed | March 7, 2026, 5:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4f00722c08190b5c42fc75fd9b7e8 |
completed | March 14, 2026, 5:20 a.m. |
Created at: March 4, 2026, 7:37 p.m.