Triple
T24505475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jedburgh Castle Jail and Museum |
E618052
|
entity |
| Predicate | notablePeriodOfUseAsPrison |
P15559
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Jedburgh Castle Jail and Museum, notablePeriodOfUseAsPrison, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeriodOfUseAsPrison Context triple: [Jedburgh Castle Jail and Museum, notablePeriodOfUseAsPrison, 19th century]
-
A.
periodOfUseAsPrison
chosen
Indicates the time span during which something functioned or was used as a prison.
-
B.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
-
C.
notablePrison
Indicates that an entity is a prison of particular significance or prominence in relation to another entity.
-
D.
dateOfNotableIncarceration
Indicates the specific date on which an entity began a notable or historically significant period of incarceration.
-
E.
wasImprisonedIn
Indicates that an entity was held in confinement or incarcerated at a particular place or facility.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.