Triple
T1547895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Poland |
E33019
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Piła |
E341962
|
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: Piła | Statement: [Greater Poland, containsCity, Piła]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piła Context triple: [Greater Poland, containsCity, Piła]
-
A.
Piła
chosen
Piła is a city in northwestern Poland known as a regional economic and transport center in the Greater Poland Voivodeship.
-
B.
Łeba
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
C.
Sopot
Sopot is a Polish Baltic Sea resort city famous for its sandy beaches, long wooden pier, and vibrant spa and nightlife culture.
-
D.
Sopot
Sopot is a suburban municipality of Belgrade, Serbia, known for its rural character and proximity to the Avala and Kosmaj mountains.
-
E.
Kościerzyna
Kościerzyna is a historic town in northern Poland known as a local cultural and economic center within the Kashubian region.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90856642c81909d88a679eb265b10 |
completed | March 5, 2026, 4:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2f394df3c819087cd773980b42f2e |
completed | March 12, 2026, 5:10 p.m. |
Created at: March 4, 2026, 7:26 p.m.