Triple
T4233578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Bohinj |
E94637
|
entity |
| Predicate | locatedInProtectedAreaSince |
P40017
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Lake Bohinj, locatedInProtectedAreaSince, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInProtectedAreaSince Context triple: [Lake Bohinj, locatedInProtectedAreaSince, 1961]
-
A.
situatedInProtectedArea
chosen
Indicates that an entity is located within the boundaries of a designated protected area (such as a reserve, park, or conservation zone).
-
B.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
C.
partOfProtectedAreaCategory
Indicates that one protected area belongs to, or is classified under, a specific protected area category.
-
D.
protectedAreaEstablished
Indicates that a designated protected area has been formally created or brought into legal existence.
-
E.
marineProtectedAreaDesignationYear
Indicates the year in which an area was formally designated as a marine protected area.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e65720c819087c4022c774ff7c3 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.