Triple
T14952172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hastings Castle |
E372821
|
entity |
| Predicate | laterStructureType |
P116812
|
FINISHED |
| Object | stone keep castle |
—
|
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: stone keep castle | Statement: [Hastings Castle, laterStructureType, stone keep castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterStructureType Context triple: [Hastings Castle, laterStructureType, stone keep castle]
-
A.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
B.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
D.
structureTypeBuilt
Indicates the type or kind of structure that was constructed in a building or creation event.
-
E.
superstructureType
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
- F. None of above. chosen
Provenance (4 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded690f2e08190ad9dad6dc05a164a |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:39 a.m.