Triple
T17367338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingarth |
E422217
|
entity |
| Predicate | religiousHeritagePeriod |
P41036
|
FINISHED |
| Object | early 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: early medieval period | Statement: [Kingarth, religiousHeritagePeriod, early medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousHeritagePeriod Context triple: [Kingarth, religiousHeritagePeriod, early medieval period]
-
A.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
B.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
C.
locatedInHistoricPeriod
chosen
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
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.
venerationPeriod
Indicates the span of time during which an entity is or was actively venerated, revered, or worshipped.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a661fc08190a4c386125bddb16b |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.