Triple

T38087520
Position Surface form Disambiguated ID Type / Status
Subject Taiwan national park system E951012 entity
Predicate appliesZoning P6793 FINISHED
Object ecological protection area 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: ecological protection area | Statement: [Taiwan national park system, appliesZoning, ecological protection area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesZoning
Context triple: [Taiwan national park system, appliesZoning, ecological protection area]
  • A. usesZoning
    Indicates that one entity applies or relies on a zoning scheme, classification, or regulations established or provided by another entity.
  • B. hasZoningPolicy
    Indicates that a governing body or authority has established or adopted a specific zoning policy that regulates land use or development within its jurisdiction.
  • C. hasZoningApproach
    Indicates the type or method of zoning policy or strategy that is applied to or associated with an entity.
  • D. hasZone chosen
    Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
  • E. zonedTo
    Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of 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_69f76f03a3608190a73fd6df87c792a8 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69ffc516d1908190b475f5a6156b0ca8 completed May 9, 2026, 11:36 p.m.
PD Predicate disambiguation batch_69ffc4a946e08190b3535a5dc15ac484 completed May 9, 2026, 11:35 p.m.
Created at: May 3, 2026, 4:21 p.m.