Triple
T20448604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Grabowsky |
E501584
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Grabowsky |
—
|
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: Grabowsky | Statement: [Paul Grabowsky, hasFamilyName, Grabowsky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grabowsky Context triple: [Paul Grabowsky, hasFamilyName, Grabowsky]
-
A.
Grabowsky
chosen
Grabowsky is a surname most notably associated with Australian pianist, composer, and conductor Paul Grabowsky.
-
B.
Grabowski
Grabowski is a Polish-origin surname borne by numerous individuals across fields such as sports, arts, and public life.
-
C.
Sosnkowski
Sosnkowski is a Polish surname most notably borne by Kazimierz Sosnkowski, a prominent Polish general and political figure of the 20th century.
-
D.
Komorowski
Komorowski is a Polish surname most prominently associated with Bronisław Komorowski, a former President of Poland.
-
E.
Grabski
Grabski is a Polish surname most notably associated with Władysław Grabski, an economist and statesman who served as Prime Minister of 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68cff1bcc8190bfc843686be117cb |
completed | April 20, 2026, 8:30 p.m. |
Created at: April 16, 2026, 11:32 a.m.