Triple
T30331507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oare, Kent |
E771491
|
entity |
| Predicate | hasNatureReserveManager |
P26654
|
FINISHED |
| Object | Kent Wildlife Trust |
—
|
NE NERFINISHED |
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: Kent Wildlife Trust | Statement: [Oare, Kent, hasNatureReserveManager, Kent Wildlife Trust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNatureReserveManager Context triple: [Oare, Kent, hasNatureReserveManager, Kent Wildlife Trust]
-
A.
containsNatureReserve
Indicates that one entity geographically includes or encompasses a designated nature reserve within its boundaries.
-
B.
hasNearbyNatureReserve
Indicates that one place or entity is located close to a designated nature reserve.
-
C.
natureReserveSince
Indicates that an area has held the legal or official status of a nature reserve since a specified point in time.
-
D.
hasConservationManagementBy
Indicates that an entity is subject to conservation management activities carried out or overseen by a specified agent or organization.
-
E.
managesProtectedArea
chosen
Indicates that an entity has responsibility for overseeing, administering, and caring for a designated protected area.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 29, 2026, 7:53 p.m.