Triple
T6455062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peak District National Park Management Plan |
E139970
|
entity |
| Predicate | isPeriodically |
P7407
|
FINISHED |
| Object | reviewed |
—
|
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: reviewed | Statement: [Peak District National Park Management Plan, isPeriodically, reviewed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPeriodically Context triple: [Peak District National Park Management Plan, isPeriodically, reviewed]
-
A.
tienePeriodicidad
chosen
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
B.
isNonPeriodic
Indicates that the subject does not occur, repeat, or follow a pattern at regular intervals over time.
-
C.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
D.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
E.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d339788190992e3299ffe30d58 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.