Triple
T15325516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acre Prison break |
E366397
|
entity |
| Predicate | prisonUse |
P22043
|
FINISHED |
| Object | detention of Jewish underground members |
—
|
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: detention of Jewish underground members | Statement: [Acre Prison break, prisonUse, detention of Jewish underground members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prisonUse Context triple: [Acre Prison break, prisonUse, detention of Jewish underground members]
-
A.
usedForImprisoning
chosen
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
-
B.
periodOfUseAsPrison
Indicates the time span during which something functioned or was used as a prison.
-
C.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
D.
hasPrison
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
-
E.
prisonType
Indicates the specific category or classification of a prison associated with an 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dfd8f048190831b463a2728eafe |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.