Triple
T3500447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area of Outstanding Natural Beauty |
E73952
|
entity |
| Predicate | managementPlanPeriod |
P302
|
FINISHED |
| Object | 5 years |
—
|
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: 5 years | Statement: [Area of Outstanding Natural Beauty, managementPlanPeriod, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementPlanPeriod Context triple: [Area of Outstanding Natural Beauty, managementPlanPeriod, 5 years]
-
A.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
B.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
C.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
D.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd4eb308190b84e84261ceec229 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.