Triple
T24505455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jedburgh Castle Jail and Museum |
E618052
|
entity |
| Predicate | demolishedStructureDemolitionYear |
P74976
|
FINISHED |
| Object | 1409 |
—
|
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: 1409 | Statement: [Jedburgh Castle Jail and Museum, demolishedStructureDemolitionYear, 1409]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolishedStructureDemolitionYear Context triple: [Jedburgh Castle Jail and Museum, demolishedStructureDemolitionYear, 1409]
-
A.
demolitionYearApprox
Indicates that an entity was demolished in or around a particular year, where the year is an approximate rather than an exact value.
-
B.
originalStructureDemolishedYear
chosen
Indicates the year in which the original structure associated with the subject was demolished.
-
C.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
D.
dateOfDemolition
Indicates the specific date on which a structure or object was demolished.
-
E.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of 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_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.