Triple
T802498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrocław |
E17157
|
entity |
| Predicate | twinCity |
P1072
|
FINISHED |
| Object | Gothenburg |
E18121
|
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: Gothenburg | Statement: [Wrocław, twinCity, Gothenburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gothenburg Context triple: [Wrocław, twinCity, Gothenburg]
-
A.
Gothenburg
chosen
Gothenburg is Sweden’s second-largest city, a major port on the country’s west coast known for its maritime heritage, universities, and vibrant cultural scene.
-
B.
Stockholm
Stockholm is the capital city of Sweden, renowned for its historic architecture, cultural institutions, and role as a major political, economic, and scientific center in Scandinavia.
-
C.
Uppsala
Uppsala is a historic Swedish city north of Stockholm, known for its prestigious university, medieval cathedral, and role as a cultural and ecclesiastical center.
-
D.
Jönköping
Jönköping is a city in southern Sweden, located at the southern end of Lake Vättern and known as a regional commercial and logistical hub.
-
E.
Linköping
Linköping is a major city in southern Sweden known for its university, high-tech industry, and historic cathedral.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4aabd9fc081908ccadd8e8769de2d |
completed | March 1, 2026, 9:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7c00e3fb48190a242264358413b05 |
completed | March 4, 2026, 5:15 a.m. |
Created at: March 1, 2026, 7:38 p.m.