Triple

T12746915
Position Surface form Disambiguated ID Type / Status
Subject Lublin Land E304628 entity
Predicate hasMajorCity P316 FINISHED
Object Puławy E392000 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: Puławy | Statement: [Lublin Land, hasMajorCity, Puławy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Puławy
Context triple: [Lublin Land, hasMajorCity, Puławy]
  • A. Puławy chosen
    Puławy is a historic town in eastern Poland known for its classical palace-and-park complex and role as an important cultural and scientific center.
  • B. Puławy
    Puławy is a village in southeastern Poland located within the administrative district of Gmina Rymanów in the Subcarpathian Voivodeship.
  • C. Zolkiewka
    Zolkiewka is a village in eastern Poland, historically home to a significant Jewish community before World War II.
  • D. Pińczów
    Pińczów is a historic town in south-central Poland known for its Renaissance architecture and scenic location in the Nida River valley.
  • E. Krasnystaw
    Krasnystaw is a town in eastern Poland known for its agricultural surroundings and annual Chmielaki beer and hops festival.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96bd58d30819082af4edb4cd0b4ab completed April 10, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8c514c481908ffff413c3873b0b completed May 3, 2026, 2:53 a.m.
Created at: April 9, 2026, 5:27 p.m.