Triple
T12735023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veľká Fatra National Park |
E304338
|
entity |
| Predicate | previousProtectionEstablished |
P106628
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [Veľká Fatra National Park, previousProtectionEstablished, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousProtectionEstablished Context triple: [Veľká Fatra National Park, previousProtectionEstablished, 1973]
-
A.
previousProtectionStatus
Indicates the protection or security state an entity was in before its current protection status.
-
B.
previouslyAllowed
Indicates that an action or relationship was permitted at some earlier time, though it may not be allowed now.
-
C.
previousRegistration
Indicates that an entity has been registered at an earlier time or in a prior instance relative to the current context.
-
D.
previouslyOutside
Indicates that an entity was located outside a specified area or boundary at some earlier time prior to the current reference point.
-
E.
protectionPolicy
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.