Triple
T37695213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettlethorpe, Lincolnshire |
E938908
|
entity |
| Predicate | historicallyAssociatedPeriod |
P4928
|
FINISHED |
| Object | medieval period |
—
|
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 period | Statement: [Kettlethorpe, Lincolnshire, historicallyAssociatedPeriod, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyAssociatedPeriod Context triple: [Kettlethorpe, Lincolnshire, historicallyAssociatedPeriod, medieval period]
-
A.
containsHistoricPeriod
Indicates that one entity encompasses or includes a specific historic period within its temporal or contextual scope.
-
B.
historicalPeriodOfSignificance
chosen
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
C.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
D.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
E.
historicalDocumentationPeriod
Indicates the time span during which something is documented or recorded in historical sources.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:18 p.m.