Triple

T14940815
Position Surface form Disambiguated ID Type / Status
Subject Zdzisław Lubomirski E372520 entity
Predicate familyName P18 FINISHED
Object Lubomirski E866817 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: Lubomirski | Statement: [Zdzisław Lubomirski, familyName, Lubomirski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lubomirski
Context triple: [Zdzisław Lubomirski, familyName, Lubomirski]
  • A. Lubomirski family chosen
    The Lubomirski family is a prominent Polish noble (szlachta) lineage historically influential in politics, military affairs, and culture of the Polish–Lithuanian Commonwealth.
  • B. Tarnowski
    Tarnowski is a Polish surname historically associated with several notable figures in Polish nobility, politics, and culture.
  • C. Gabrilowitsch
    Gabrilowitsch is a surname most notably associated with Ossip Gabrilowitsch, a Russian-born American pianist, conductor, and son-in-law of Mark Twain.
  • D. Leszczyński
    Leszczyński is a Polish noble surname most famously borne by Stanisław Leszczyński, a former King of Poland and Duke of Lorraine.
  • E. Wasilewski
    Wasilewski is a Polish surname, typically indicating familial or geographic origin and commonly found in Poland and among the Polish diaspora.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded64a2f24819099b21566756668a2 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe7e929f3881908560b8428e72327d completed May 9, 2026, 12:23 a.m.
Created at: April 10, 2026, 2:38 a.m.