Triple
T19378095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor’s House, Lancaster Castle |
E484723
|
entity |
| Predicate | isWithinFortification |
P28661
|
FINISHED |
| Object | medieval and later castle complex |
—
|
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: medieval and later castle complex | Statement: [Governor’s House, Lancaster Castle, isWithinFortification, medieval and later castle complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinFortification Context triple: [Governor’s House, Lancaster Castle, isWithinFortification, medieval and later castle complex]
-
A.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
B.
hasFortificationNearby
Indicates that one entity is located in proximity to, or within the immediate area of, a fortification structure associated with it.
-
C.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
-
D.
locatedInFortress
chosen
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
E.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5dc3048190830b55c8ca02e624 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.