Triple
T13617288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popławski |
E325349
|
entity |
| Predicate | hasPluralForm |
P5088
|
FINISHED |
| Object | Popławscy |
E325349
|
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: Popławscy | Statement: [Popławski, hasPluralForm, Popławscy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Popławscy Context triple: [Popławski, hasPluralForm, Popławscy]
-
A.
Popławska
Popławska is the feminine form of the Polish surname Popławski.
-
B.
Popławski
chosen
Popławski is a Polish surname commonly borne by individuals of Polish origin.
-
C.
Dąbrowscy
Dąbrowscy is the Polish plural surname form referring collectively to members of the Dąbrowski family.
-
D.
Potocki
Potocki is a Polish noble surname historically associated with one of the most prominent aristocratic families of the Polish–Lithuanian Commonwealth.
-
E.
Żółkiewski family
The Żółkiewski family was a prominent Polish noble (szlachta) lineage of the Polish–Lithuanian Commonwealth, best known for producing the distinguished military commander and statesman Stanisław Żółkiewski.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0ae77e0819081e3b14642460dc6 |
completed | April 12, 2026, 2:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78ae7d6908190836172e955b0d7e8 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:50 p.m.