Triple
T22684283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İmralı F-Type High-Security Closed Prison |
E560867
|
entity |
| Predicate | visitationRules |
P97399
|
FINISHED |
| Object | strictly controlled |
—
|
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: strictly controlled | Statement: [İmralı F-Type High-Security Closed Prison, visitationRules, strictly controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitationRules Context triple: [İmralı F-Type High-Security Closed Prison, visitationRules, strictly controlled]
-
A.
relativeVisitation
Indicates that one entity visits or spends time with another entity in the capacity of a relative or family member.
-
B.
visitorGuideline
chosen
Indicates guidelines or rules that specify how visitors are expected or allowed to behave or proceed in a particular context.
-
C.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
D.
annualVisitation
Indicates a recurring visit or attendance that takes place once every year between the related entities.
-
E.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17862c8a48190912a8ad09dfda795 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:12 p.m.