Triple
T29033662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parque Natural |
E737793
|
entity |
| Predicate | zoningMayInclude |
P132063
|
FINISHED |
| Object | strict protection zones |
—
|
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: strict protection zones | Statement: [Parque Natural, zoningMayInclude, strict protection zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoningMayInclude Context triple: [Parque Natural, zoningMayInclude, strict protection zones]
-
A.
hasZoningRestriction
Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
-
B.
zoningAuthority
Indicates that an entity has official power or jurisdiction to regulate land use and development within a specified area.
-
C.
usesZoning
Indicates that one entity applies or relies on a zoning scheme, classification, or regulations established or provided by another entity.
-
D.
hasZoningMix
Indicates that an area or property is subject to a combination of different zoning designations or land-use categories.
-
E.
zonesInclude
chosen
Indicates that one zone spatially or logically contains or encompasses another zone.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603acd608190b7e0ed75d26b6799 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:57 a.m.