Triple
T26209298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allington Castle, Kent |
E655439
|
entity |
| Predicate | originatesFromPeriod |
P38044
|
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: [Allington Castle, Kent, originatesFromPeriod, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromPeriod Context triple: [Allington Castle, Kent, originatesFromPeriod, medieval period]
-
A.
timePeriodOrigin
chosen
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
B.
developedFromPeriod
Indicates that something originated, evolved, or was derived from a specified historical or temporal period.
-
C.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
D.
periodOfOriginOfSourceWork
Indicates the historical time period during which the original source work was created or first came into existence.
-
E.
chroniclesPeriodFrom
Indicates that something documents or records events starting from a specified point in time or historical period.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 26, 2026, 8:51 p.m.