Triple

T22985186
Position Surface form Disambiguated ID Type / Status
Subject Kowal E571586 entity
Predicate hasNameInLanguage P15 FINISHED
Object Kowal@en 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: Kowal@en | Statement: [Kowal, hasNameInLanguage, Kowal@en]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kowal@en
Context triple: [Kowal, hasNameInLanguage, Kowal@en]
  • A. Kowalczyk
    Kowalczyk is a common Polish surname, typically a diminutive or variant of Kowal/Kowalski, historically associated with the occupation of a blacksmith.
  • B. Kowal chosen
    Kowal is a small town in central Poland historically notable as the birthplace of King Casimir III the Great.
  • C. Kowen
    Kowen is a locality within the Kowen Forest area near Canberra in the Australian Capital Territory, known for its pine plantations and outdoor recreation activities.
  • D. Kowalik
    Kowalik is a Polish surname, likely of similar origin or family line to the surname Kowalski.
  • E. Kakowski
    Kakowski is a Polish surname most notably borne by Aleksander Kakowski, a prominent Roman Catholic cardinal and archbishop in early 20th-century 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_69e245b3c50481908bb3741ec9f40862 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18298637c819086fca34d55bad22d completed April 29, 2026, 4:01 a.m.
Created at: April 17, 2026, 3:49 p.m.