Triple
T37343928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tora Liman Prison |
E927117
|
entity |
| Predicate | visitationRights |
P187751
|
FINISHED |
| Object | tightly 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: tightly controlled | Statement: [Tora Liman Prison, visitationRights, tightly controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitationRights Context triple: [Tora Liman Prison, visitationRights, tightly controlled]
-
A.
relativeVisitation
Indicates that one entity visits or spends time with another entity in the capacity of a relative or family member.
-
B.
custody
Indicates having legal responsibility and authority over the care and control of another entity, typically a child or dependent.
-
C.
annualVisitation
Indicates a recurring visit or attendance that takes place once every year between the related entities.
-
D.
visits
Indicates that one entity goes to or spends time at the location or presence of another entity.
-
E.
custodyModel
Indicates the type or structure of custodial responsibility or control that one party holds over another party or asset.
- F. None of above. chosen
Provenance (4 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.