Triple
T30208323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Slains Castle |
E767998
|
entity |
| Predicate | visitPeriod |
P162720
|
FINISHED |
| Object | late 19th 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: late 19th century | Statement: [New Slains Castle, visitPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitPeriod Context triple: [New Slains Castle, visitPeriod, late 19th century]
-
A.
peakVisitorPeriod
chosen
Indicates the time period during which a place or attraction experiences its highest number of visitors.
-
B.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
C.
scopeOfVisits
Indicates the range, extent, or boundaries within which visits or visiting activities occur or are applicable.
-
D.
hasVisitingTime
Indicates that there is a specified time period during which visits are allowed or scheduled for an entity.
-
E.
visitYear
Indicates the specific year in which a visit or visitation event took place.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67fca43448190b108c8c1b998738f |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:32 p.m.