Triple
T24147756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yerseke |
E598432
|
entity |
| Predicate | hasProtectionStatusNearby |
P41708
|
FINISHED |
| Object | Oosterschelde National Park |
—
|
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: Oosterschelde National Park | Statement: [Yerseke, hasProtectionStatusNearby, Oosterschelde National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectionStatusNearby Context triple: [Yerseke, hasProtectionStatusNearby, Oosterschelde National Park]
-
A.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
B.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
C.
isProtectedAreaStatus
chosen
Indicates that an entity has a designated protection status, typically signifying legal or formal recognition as a protected area.
-
D.
previousProtectionStatus
Indicates the protection or security state an entity was in before its current protection status.
-
E.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00c42288190843962f9476a94a1 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.