Triple
T36728756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauwersmeer |
E907269
|
entity |
| Predicate | openedToPublicAsNationalPark |
P127815
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Lauwersmeer, openedToPublicAsNationalPark, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToPublicAsNationalPark Context triple: [Lauwersmeer, openedToPublicAsNationalPark, 2003]
-
A.
openedAsNationalPark
chosen
Indicates that a location or area was officially designated and inaugurated as a national park at a specific time.
-
B.
openedAsStatePark
Indicates that a location or area was officially inaugurated and made available to the public as a state park.
-
C.
establishedAsPark
Indicates that an area or site has been officially designated and recognized as a park.
-
D.
openedToPublicAsRecreationArea
Indicates that a place was made accessible to the general public specifically for recreational use.
-
E.
establishedAsNationalParkReserve
Indicates that an area has been formally designated and protected as a national park reserve by an authorized governing body.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:12 p.m.