Triple
T16066860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downshire House |
E389755
|
entity |
| Predicate | hasPlanningProtection |
P24929
|
FINISHED |
| Object | listed building consent required for alterations |
—
|
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: listed building consent required for alterations | Statement: [Downshire House, hasPlanningProtection, listed building consent required for alterations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningProtection Context triple: [Downshire House, hasPlanningProtection, listed building consent required for alterations]
-
A.
hasPlanningStatus
chosen
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
B.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
C.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
D.
hasPlanningSignificance
Indicates that something holds importance or relevance for planning, decision-making, or future organizational activities.
-
E.
hasPlanningContext
Indicates that an entity is associated with a specific planning-related situation, scope, or set of conditions that frame how it should be interpreted or used.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.