Triple

T24167818
Position Surface form Disambiguated ID Type / Status
Subject Polish landscape parks network E599038 entity
Predicate includesZones P6793 FINISHED
Object areas with varying degrees of protection 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: areas with varying degrees of protection | Statement: [Polish landscape parks network, includesZones, areas with varying degrees of protection]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesZones
Context triple: [Polish landscape parks network, includesZones, areas with varying degrees of protection]
  • A. zonesInclude
    Indicates that one zone spatially or logically contains or encompasses another zone.
  • B. hasZone chosen
    Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
  • C. qualifyingZones
    Indicates that certain areas or regions meet specified criteria or conditions required for a particular status, activity, or classification.
  • D. fareZoneIncludes
    Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
  • E. includesMetropolitanZone
    Indicates that one geographic or administrative area contains or encompasses a designated metropolitan zone within its boundaries.
  • 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_69e288cbd62881909de32ca64a70c17b completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f27c9ddfcc819096697a844b300cce completed April 29, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f1c42f942c8190b103ff29a60fef34 completed April 29, 2026, 8:41 a.m.
Created at: April 17, 2026, 11:33 p.m.