Triple
T8023406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avon Green Belt |
E186792
|
entity |
| Predicate | planningPolicyType |
P8653
|
FINISHED |
| Object | strategic planning designation |
—
|
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: strategic planning designation | Statement: [Avon Green Belt, planningPolicyType, strategic planning designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningPolicyType Context triple: [Avon Green Belt, planningPolicyType, strategic planning designation]
-
A.
planningPolicy
Indicates that one entity establishes or defines rules, guidelines, or strategies governing how another entity should plan or make planning-related decisions.
-
B.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
C.
advancedPolicyOf
Indicates that one policy is a more developed, detailed, or progressive version of another policy.
-
D.
decisionPublicationPolicy
Indicates the policy or rules governing how decisions are made public or communicated.
-
E.
hasPlanningPattern
Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8fb6788190a16413051ec26988 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.