Triple

T6538479
Position Surface form Disambiguated ID Type / Status
Subject Battle of Tomaszów Lubelski E168225 entity
Predicate location P40 FINISHED
Object Tomaszów Lubelski E479235 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: Tomaszów Lubelski | Statement: [Battle of Tomaszów Lubelski, location, Tomaszów Lubelski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tomaszów Lubelski
Context triple: [Battle of Tomaszów Lubelski, location, Tomaszów Lubelski]
  • A. Tomaszów Lubelski chosen
    Tomaszów Lubelski is a town in eastern Poland known for its historical wooden architecture and location near the Roztocze National Park.
  • B. Słubice
    Słubice is a Polish border town on the Oder River, located directly across from Frankfurt (Oder) and historically part of the same urban area.
  • C. Ostrołęka
    Ostrołęka is a town in east-central Poland known for its historical role in the Napoleonic Wars and as a local industrial and administrative center.
  • D. Mielec
    Mielec is a town in southeastern Poland known for its aviation industry and manufacturing sector.
  • E. Bolesławiec
    Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
  • 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_69c68a51564081909e93aee0dbd9cca3 completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6add4b7f881909e485325c353f51c completed March 27, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69d2281e332c819093444685d37b9251 completed April 5, 2026, 9:15 a.m.
Created at: March 27, 2026, 1:49 p.m.