Triple
T13157670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exeter, Devon, England |
E312631
|
entity |
| Predicate | historicalCountyTownSince |
P13121
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Exeter, Devon, England, historicalCountyTownSince, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCountyTownSince Context triple: [Exeter, Devon, England, historicalCountyTownSince, 13th century]
-
A.
hasHistoricCountySeat
chosen
Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
-
B.
historicalCounty
Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
-
C.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
D.
historicalTownshipOf
Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
-
E.
historicalCountyChange
Indicates that a county’s administrative boundaries or status have been altered over time, such as through creation, dissolution, merger, or territorial reassignment.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.