Triple
T23185350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pławy |
E579575
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Pławy (Polish) |
—
|
NE NERFINISHED |
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ławy (Polish) | Statement: [Pławy, hasNameInLanguage, Pławy (Polish)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pławy (Polish) Context triple: [Pławy, hasNameInLanguage, Pławy (Polish)]
-
A.
Pławy
chosen
Pławy is a village in southern Poland located in the administrative district of Gmina Oświęcim in Lesser Poland Voivodeship.
-
B.
Pławidło
Pławidło is a village in western Poland located within the administrative district of Gmina Słubice in the Lubusz Voivodeship.
-
C.
PŁ
PŁ is the Polish abbreviation for Łódź University of Technology, a major technical university located in Łódź, Poland.
-
D.
Paniowy
Paniowy is a district of the town of Mikołów in southern Poland, located in the Silesian region.
-
E.
Błonie (Polish)
Błonie (Polish) is a town in east-central Poland, located west of Warsaw, known historically as part of the former Congress Poland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f7230208190820acf52f537b3ff |
completed | April 29, 2026, 4:56 a.m. |
Created at: April 17, 2026, 4:05 p.m.