Triple

T20120440
Position Surface form Disambiguated ID Type / Status
Subject Apostle of Warsaw E490591 entity
Predicate hasContext P36 FINISHED
Object Warsaw 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: Warsaw | Statement: [Apostle of Warsaw, hasContext, Warsaw]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Warsaw
Context triple: [Apostle of Warsaw, hasContext, Warsaw]
  • A. Warsaw chosen
    Warsaw is the capital and largest city of Poland, known for its resilient history, especially its near-total destruction in World War II and subsequent postwar reconstruction.
  • B. Warsaw
    Warsaw is a small city in northern Indiana known as the "Orthopedic Capital of the World" for its concentration of medical device manufacturers.
  • C. Warsaw
    Warsaw was the original name of the English post-punk band that later became known as Joy Division.
  • D. Lublin
    Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
  • E. Ville de Varsovie
    Ville de Varsovie was a French ship of the line that took part in the early 19th-century naval engagement known as the Battle of the Basque Roads.
  • 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_69da62636cc08190982cc71733a17b8d completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e6673cfaac81909d6216f3e37c2439 completed April 20, 2026, 5:49 p.m.
Created at: April 11, 2026, 11:30 p.m.