Triple
T22154534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingswear Castle area |
E547499
|
entity |
| Predicate | heritagePeriodOfDominantStructure |
P103862
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Kingswear Castle area, heritagePeriodOfDominantStructure, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritagePeriodOfDominantStructure Context triple: [Kingswear Castle area, heritagePeriodOfDominantStructure, 16th century]
-
A.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
B.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
C.
timePeriodOfArchitecture
chosen
Indicates the historical time period or era during which a particular architectural work, style, or feature was created or predominantly used.
-
D.
heritageSince
Indicates that a heritage status, tradition, or cultural legacy has been in effect or recognized starting from a specific point in time.
-
E.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f6d5b88190badee2e515a3b633 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.