Triple

T25325516
Position Surface form Disambiguated ID Type / Status
Subject Chęciny County E635000 entity
Predicate partOfHistoricalUnit P5057 FINISHED
Object Sandomierz Land 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: Sandomierz Land | Statement: [Chęciny County, partOfHistoricalUnit, Sandomierz Land]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partOfHistoricalUnit
Context triple: [Chęciny County, partOfHistoricalUnit, Sandomierz Land]
  • A. partOfHistoricalArea
    Indicates that one entity is located within or belongs to a designated historical area or heritage zone.
  • B. historicallyPartOf chosen
    Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
  • C. partOfHistoricalPeople
    Indicates that one entity is a subset, member, or component of a larger group or collection of historical people.
  • D. historicalEntityWithin
    Indicates that one historical entity is geographically, administratively, or contextually contained within another historical entity.
  • E. historicalEntityAssociated
    Indicates that one entity has a documented historical connection, relevance, or involvement with another entity.
  • F. None of above.

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_69e75a9908108190a95427a97020632a completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f69383222c81909d8baa04129d5c81 completed May 3, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69f690eb1e948190aab41a89969519a5 completed May 3, 2026, 12:03 a.m.
Created at: April 21, 2026, 1:30 p.m.