Triple
T35446055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beemster Lake |
E1024487
|
entity |
| Predicate | heritageSuccessorInscriptionYear |
P193153
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Beemster Lake, heritageSuccessorInscriptionYear, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageSuccessorInscriptionYear Context triple: [Beemster Lake, heritageSuccessorInscriptionYear, 1999]
-
A.
heritageRevelationYear
Indicates the year in which a particular heritage status, designation, or significance was formally revealed, recognized, or made public.
-
B.
firstInscriptionYear
Indicates the year in which an entity was first inscribed, recorded, or officially entered into a relevant register or list.
-
C.
includedInMonumentYear
Indicates that an entity was incorporated into or recognized as part of a monument in a specific year.
-
D.
yearOfMonument
Indicates the specific year in which a monument was established, built, or officially dedicated.
-
E.
inscribedOnUNESCOListInYear
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
- F. None of above. chosen
Provenance (4 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:04 p.m.