Triple
T12189483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkcudbrightshire |
E290423
|
entity |
| Predicate | hasHistoricCountyStatusAbolished |
P41542
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Kirkcudbrightshire, hasHistoricCountyStatusAbolished, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCountyStatusAbolished Context triple: [Kirkcudbrightshire, hasHistoricCountyStatusAbolished, 1975]
-
A.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
B.
historicCountyAbolishedAsAdministrativeUnit
chosen
Indicates that a historic county ceased to function as an official administrative unit.
-
C.
hasHistoricCountyCode
Indicates that an entity is associated with a specific historic county, identified by its county code.
-
D.
hasHistoricCountyNumber
Indicates that an entity is associated with a specific identifier corresponding to its historic county designation.
-
E.
hasHistoricCountySeat
Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.