Triple
T35446056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beemster Lake |
E1024487
|
entity |
| Predicate | heritageSuccessorCategory |
P5929
|
FINISHED |
| Object | cultural landscape |
—
|
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: cultural landscape | Statement: [Beemster Lake, heritageSuccessorCategory, cultural landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageSuccessorCategory Context triple: [Beemster Lake, heritageSuccessorCategory, cultural landscape]
-
A.
heritageSuccessor
Indicates that one entity is the successor or inheritor of another in terms of heritage, lineage, or cultural tradition.
-
B.
heritageSuccessorName
Indicates that one entity is the named successor in a heritage or legacy relationship to another entity.
-
C.
heritageFor
Indicates that something serves as a source, basis, or contributing legacy for another entity’s heritage or tradition.
-
D.
heritageType
chosen
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
E.
heritagePrecursor
Indicates that one entity serves as an ancestral or foundational predecessor in the heritage or lineage of another entity.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:04 p.m.