Triple
T37316725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnum |
E926355
|
entity |
| Predicate | nearbyModernProtectedArea |
P67111
|
FINISHED |
| Object | Krka 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: Krka National Park | Statement: [Burnum, nearbyModernProtectedArea, Krka National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyModernProtectedArea Context triple: [Burnum, nearbyModernProtectedArea, Krka National Park]
-
A.
stateProtectedAreasNearby
Indicates that there are state-protected natural or conservation areas located close to the referenced entity.
-
B.
nearbyProtectedAreaType
Indicates that an entity is located near a protected area and specifies the type or category of that nearby protected area.
-
C.
nearbyProtectedSite
chosen
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
-
D.
nearestMajorProtectedArea
Indicates the closest significant legally protected natural area to a given location or entity.
-
E.
isInlandWaterProtectedAreaNearby
Indicates that there is a protected inland water area located in close proximity to the referenced 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 3, 2026, 4:16 p.m.