Triple
T25991916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaya River |
E646375
|
entity |
| Predicate | hasProtectedAreasAlongCourse |
P42405
|
FINISHED |
| Object | Podyjí National Park |
—
|
NE NERFINISHED |
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: Podyjí National Park | Statement: [Thaya River, hasProtectedAreasAlongCourse, Podyjí National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedAreasAlongCourse Context triple: [Thaya River, hasProtectedAreasAlongCourse, Podyjí National Park]
-
A.
hasProtectedAreaAlongCourse
chosen
Indicates that a segment of the course or route passes through or borders a designated protected area.
-
B.
hasProtectedAreasNearby
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
C.
hasProtectedArea
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
-
D.
hasProtectedAreaOnSlopes
Indicates that a designated protected area exists specifically on the slopes of a landform or terrain.
-
E.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 22, 2026, 8:57 a.m.