Triple
T11083385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armia „Łódź” |
E262056
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | city of Łódź |
E15327
|
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: city of Łódź | Statement: [Armia „Łódź”, namedAfter, city of Łódź]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Łódź Context triple: [Armia „Łódź”, namedAfter, city of Łódź]
-
A.
Łódź
chosen
Łódź is one of Poland’s largest cities, historically known as a major industrial and textile manufacturing center.
-
B.
Łódź Fabryczna
Łódź Fabryczna is a major modern railway terminus in Łódź, Poland, serving as one of the city’s primary long-distance and regional train hubs.
-
C.
Lublin
Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
-
D.
Wrocław
Wrocław is a major historic city in southwestern Poland, known for its picturesque Old Town, numerous bridges over the Oder River, and role as a cultural and academic center.
-
E.
Kalisz
Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799bf89f48190889f08d2f5dd220a |
completed | April 9, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e79854c88190bda69cfbe4ae9d1e |
completed | April 18, 2026, 8:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.