Triple

T17843712
Position Surface form Disambiguated ID Type / Status
Subject Iwanowice E445599 entity
Predicate hasOfficialName P66 FINISHED
Object Iwanowice 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: Iwanowice | Statement: [Iwanowice, hasOfficialName, Iwanowice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iwanowice
Context triple: [Iwanowice, hasOfficialName, Iwanowice]
  • A. Iwanowice chosen
    Iwanowice is a village in southern Poland that serves as the administrative seat of the local Gmina Iwanowice in the Lesser Poland Voivodeship.
  • B. Rakowice
    Rakowice is a historic district in Kraków, Poland, known for its large military cemetery and proximity to the city center.
  • C. Wojnowo
    Wojnowo is a village in western Poland that was formerly known by its German name Reckenwalde.
  • D. Grodkowo
    Grodkowo is a settlement in northern Poland located within the Warmian-Masurian Voivodeship, a region known for its lakes and natural landscapes.
  • E. Radziejowa
    Radziejowa is a prominent mountain peak in southern Poland, known for its forested slopes, scenic views, and status as the highest summit of the Beskid Sądecki range.
  • 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_69d8b9f1a6d881909f024bc603111cdb completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ff8730881908cc8e1b572fa0af8 completed April 19, 2026, 8:19 a.m.
Created at: April 10, 2026, 10:16 a.m.