Triple
T22087209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botos Lake |
E545810
|
entity |
| Predicate | humanActivitiesRestricted |
P90556
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Botos Lake, humanActivitiesRestricted, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanActivitiesRestricted Context triple: [Botos Lake, humanActivitiesRestricted, yes]
-
A.
activitiesRestricted
chosen
Indicates that certain actions or behaviors are limited, prohibited, or constrained under specified conditions or for particular entities.
-
B.
mayRestrictActivity
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
-
C.
movementRestrictions
Indicates limitations, rules, or prohibitions that constrain how, where, or when an entity is allowed to move.
-
D.
hasRecreationalUseRestriction
Indicates that there is a limitation or prohibition on how an entity may be used for recreational purposes.
-
E.
permittedActivity
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e2e3108190883199f272756e4e |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.