Triple
T16625992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Łączyńska |
E403944
|
entity |
| Predicate | maidenName |
P18
|
FINISHED |
| Object | Łączyńska |
E403944
|
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: Łączyńska | Statement: [Maria Łączyńska, maidenName, Łączyńska]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łączyńska Context triple: [Maria Łączyńska, maidenName, Łączyńska]
-
A.
Łączyńska
chosen
Łączyńska is the Polish maiden surname of Maria Walewska, a noblewoman known as a mistress of Napoleon Bonaparte.
-
B.
Nowakówna
Nowakówna is the traditional Polish feminine surname form derived from the common family name Nowak, historically used to denote an unmarried daughter in the Nowak family.
-
C.
Zawadzkie
Zawadzkie is a small town in southwestern Poland known for its industrial heritage and location within the Opole region.
-
D.
Popławska
Popławska is the feminine form of the Polish surname Popławski.
-
E.
Poniatowa
Poniatowa is a town in eastern Poland historically known as the site of a Nazi German forced labor camp during World War II.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e375530ed081908337dc5c6360d733 |
completed | April 18, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007dba91bc819090a78ac4c0c01fc8 |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:17 a.m.