Triple
T17391780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Planning Policy Framework |
E422839
|
entity |
| Predicate | significantRevision |
P24446
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [National Planning Policy Framework, significantRevision, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantRevision Context triple: [National Planning Policy Framework, significantRevision, 2018]
-
A.
significantRevisionIn
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
-
B.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
-
C.
majorRevisionDate
chosen
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
D.
significantRestoration
Indicates that an entity has undergone a major or substantial restoration effort that notably improves or returns it to a previous condition.
-
E.
significantDevelopment
Indicates a development, change, or event that has substantial impact or importance within a given context or process.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43aba5398819096846bdeefde0788 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.