Triple

T30011141
Position Surface form Disambiguated ID Type / Status
Subject Inowrocław County E762462 entity
Predicate administrativeReformDate P5212 FINISHED
Object 1 January 1999 LITERAL 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: 1 January 1999 | Statement: [Inowrocław County, administrativeReformDate, 1 January 1999]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: administrativeReformDate
Context triple: [Inowrocław County, administrativeReformDate, 1 January 1999]
  • A. administrativeChangeDate
    Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
  • B. reformDate chosen
    Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
  • C. timeOfMajorReforms
    Indicates the specific time period during which significant reforms or major changes took place.
  • D. lastReform
    Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
  • E. timePeriodOfAdministrativeChange
    Indicates the specific time span during which an administrative change (such as creation, modification, or dissolution of an administrative unit or status) takes place.
  • 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_69f2246b0c84819094f1250b6a02d277 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fbbc49da8c8190902bbb05d2477cab completed May 6, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69fbb13f34b08190bbbb220ac1e6e666 completed May 6, 2026, 9:23 p.m.
Created at: April 29, 2026, 6:44 p.m.