Triple
T6333370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothian Island Wildlife Sanctuary |
E142432
|
entity |
| Predicate | activityRestricted |
P47306
|
FINISHED |
| Object | hunting |
—
|
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: hunting | Statement: [Lothian Island Wildlife Sanctuary, activityRestricted, hunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityRestricted Context triple: [Lothian Island Wildlife Sanctuary, activityRestricted, hunting]
-
A.
mayRestrictActivity
chosen
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
-
B.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
C.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
D.
cannotExercise
Indicates that an entity is unable or not permitted to perform physical exercise or engage in workout activities.
-
E.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06517a1e88190a0bfcac8a7e3a305 |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.