Triple
T11363764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denbigh Castle |
E269149
|
entity |
| Predicate | townDefences |
P22477
|
FINISHED |
| Object | integrated with Denbigh town walls |
—
|
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: integrated with Denbigh town walls | Statement: [Denbigh Castle, townDefences, integrated with Denbigh town walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townDefences Context triple: [Denbigh Castle, townDefences, integrated with Denbigh town walls]
-
A.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
B.
hasFortifications
chosen
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
C.
fortifiedSite
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
D.
primaryDefendedCity
Indicates that an entity served as the main or principal city that another entity was responsible for defending.
-
E.
eraOfFortification
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.