Triple
T14113050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warburton Woods |
E339691
|
entity |
| Predicate | hasManagementFocus |
P22222
|
FINISHED |
| Object | recreation and nature conservation |
—
|
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: recreation and nature conservation | Statement: [Warburton Woods, hasManagementFocus, recreation and nature conservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManagementFocus Context triple: [Warburton Woods, hasManagementFocus, recreation and nature conservation]
-
A.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
coManagementFocus
Indicates that two or more parties share responsibility and decision-making authority in managing a particular resource, project, or domain.
-
C.
hasManagementRelevance
Indicates that something is pertinent or significant to management activities, decisions, or responsibilities.
-
D.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
E.
hasManagementGoal
chosen
Indicates that an entity is associated with a specific management objective or target it is intended to achieve or support.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.