Triple
T13156358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beemster |
E312598
|
entity |
| Predicate | previouslyCoveredBy |
P108818
|
FINISHED |
| Object | inland lake |
—
|
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: inland lake | Statement: [Beemster, previouslyCoveredBy, inland lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyCoveredBy Context triple: [Beemster, previouslyCoveredBy, inland lake]
-
A.
previouslyCovered
Indicates that the subject has already been addressed, discussed, or dealt with at an earlier time or in a prior context.
-
B.
originallyCoveredBy
Indicates that something was first protected, reported on, or documented by a particular source, medium, or entity before any others.
-
C.
hasBeenCoveredBy
Indicates that something has received coverage or treatment by another entity, such as being reported on, discussed, or addressed.
-
D.
formerCover
Indicates that one entity previously served as the cover (e.g., protective or outer layer) for another entity but no longer does so.
-
E.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:12 p.m.