Triple
T16495601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widzew Łódź |
E400674
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Widzew |
E400674
|
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: Widzew | Statement: [Widzew Łódź, shortName, Widzew]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Widzew Context triple: [Widzew Łódź, shortName, Widzew]
-
A.
Widzew
chosen
Widzew is a Polish football club from Łódź known for its rich history and passionate fan base.
-
B.
Siewierz
Siewierz is a historic town in southern Poland, known for its medieval castle ruins and location within the Silesian region.
-
C.
Wolyniec
Wolyniec is a Polish-origin surname most notably associated with American soccer player and coach John Wolyniec.
-
D.
Witów
Witów is a village in southern Poland, located in the Tatra region and known as a base for exploring the nearby mountains and valleys.
-
E.
Wilczyce
Wilczyce is a village in southeastern Poland that serves as the seat of the rural administrative district Gmina Wilczyce in Sandomierz County.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e332c1c8190888a042d0192233a |
completed | April 18, 2026, 7:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a005828849481909e95c5822ed6f74d |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:14 a.m.