Triple
T16625993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Łączyńska |
E403944
|
entity |
| Predicate | marriedName |
P18
|
FINISHED |
| Object | Walewska |
E405995
|
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: Walewska | Statement: [Maria Łączyńska, marriedName, Walewska]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walewska Context triple: [Maria Łączyńska, marriedName, Walewska]
-
A.
Walewska
chosen
Walewska is a Polish surname most famously associated with Maria Walewska, a noblewoman known as the mistress of Napoleon Bonaparte.
-
B.
Wasilewska
Wasilewska is a Polish surname most notably associated with Wanda Wasilewska, a 20th-century Polish and Soviet writer and communist activist.
-
C.
Krajewska
Krajewska is the feminine form of the Polish surname Krajewski.
-
D.
Zofia
Zofia is a feminine given name of Slavic origin, particularly common in Poland and other Central and Eastern European countries.
-
E.
Śliwińska
Śliwińska is a Polish surname most notably borne by professional ballroom dancer and choreographer Edyta Śliwińska.
- 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_6a008a2b3a608190ad8d2b653cd8785d |
completed | May 10, 2026, 1:37 p.m. |
Created at: April 10, 2026, 5:17 a.m.