Triple
T36367619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pliva Lakes |
E895668
|
entity |
| Predicate | recreationalAreaFor |
P56580
|
FINISHED |
| Object | Jajce |
—
|
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: Jajce | Statement: [Pliva Lakes, recreationalAreaFor, Jajce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalAreaFor Context triple: [Pliva Lakes, recreationalAreaFor, Jajce]
-
A.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
B.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
C.
isRecreationalArea
chosen
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
D.
operatorOfRecreationArea
Indicates that an entity is responsible for managing, running, or overseeing the operations of a recreation area.
-
E.
recreationActivitiesSupported
Indicates that an entity provides, allows, or is compatible with certain recreational activities.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.