Triple
T31061502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Kesh, County Antrim, Northern Ireland |
E791551
|
entity |
| Predicate | openedAsInternmentCamp |
P9060
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Long Kesh, County Antrim, Northern Ireland, openedAsInternmentCamp, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsInternmentCamp Context triple: [Long Kesh, County Antrim, Northern Ireland, openedAsInternmentCamp, 1971]
-
A.
internmentCampClosed
Indicates that a particular internment camp has ceased operations and is no longer in use.
-
B.
wasSiteOfInternmentCamps
Indicates that the subject location served as a site where internment camps were established and operated.
-
C.
treatmentOfInternees
Indicates how individuals who are interned or detained are handled, managed, or treated by the responsible authorities or entities.
-
D.
detentionCampEstablished
chosen
Indicates that a detention camp was created and put into operation at a specific time or under specific circumstances.
-
E.
hasRefugeeCamp
Indicates that a location or entity hosts, contains, or is the site of a refugee camp.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 9:01 p.m.