Triple
T6843207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strait Island |
E157825
|
entity |
| Predicate | requiresSpecialPermitForVisit |
P53204
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Strait Island, requiresSpecialPermitForVisit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSpecialPermitForVisit Context triple: [Strait Island, requiresSpecialPermitForVisit, true]
-
A.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
B.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
-
C.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
D.
climbingPermitRequired
Indicates that performing a climbing activity at a given location or on a given route is contingent upon obtaining a formal permit or authorization.
-
E.
hasTourismRestriction
chosen
Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b7179481909e3482fef47b2719 |
completed | March 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.