Triple
T9861750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August Zaleski |
E239729
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Zaleski |
E239729
|
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: Zaleski | Statement: [August Zaleski, familyName, Zaleski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zaleski Context triple: [August Zaleski, familyName, Zaleski]
-
A.
Zaleski
chosen
Zaleski is a Polish surname most notably borne by August Zaleski, a prominent Polish diplomat and statesman who served as President of Poland in exile.
-
B.
Zaslofsky
Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
-
C.
Szaflary
Szaflary is a village in southern Poland’s Podhale region, known for its geothermal hot springs and traditional highland culture.
-
D.
Lorkowski
Lorkowski is a surname of likely Polish origin borne by individuals such as Joe Lorkowski.
-
E.
Cimoszewicz
Cimoszewicz is a Polish surname most prominently associated with Włodzimierz Cimoszewicz, a former Prime Minister and influential politician in Poland.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3b6aa108190978f1c0cdc0f45a0 |
completed | April 2, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d20d511e348190aab23a45048ea7b3 |
completed | April 5, 2026, 7:20 a.m. |
Created at: March 30, 2026, 8:35 p.m.