Triple
T21621062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tullynally Castle |
E533577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former fortified castle |
C5439
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former fortified castle Context triple: [Tullynally Castle, instanceOf, former fortified castle]
-
A.
former castle town
A former castle town is a settlement that historically developed around and was economically, socially, and administratively centered on a castle, but no longer functions in that original feudal or defensive role.
-
B.
fortified building
A fortified building is a heavily constructed structure designed with defensive features such as thick walls, limited entry points, and protective battlements to resist attacks and provide security for its occupants.
-
C.
castle remains
Castle remains are the surviving structural fragments and archaeological traces of a once-complete castle, such as ruined walls, foundations, towers, and earthworks, that reveal its former layout and historical use.
-
D.
former castle site
chosen
A former castle site is a location where a castle once stood but has since been demolished, ruined, or otherwise lost its original structure, though traces or historical evidence of the castle remain.
-
E.
fortified town
A fortified town is a settlement enclosed by defensive structures such as walls, towers, and gates, designed to protect its inhabitants and resources from external threats.
- F. None of above.
Provenance (1 batch)
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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:34 p.m.