Triple
T1327125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanarkshire |
E28353
|
entity |
| Predicate | hasHistoricSheriffdomStatus |
P27242
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lanarkshire, hasHistoricSheriffdomStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSheriffdomStatus Context triple: [Lanarkshire, hasHistoricSheriffdomStatus, true]
-
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.
hasHistoricCountySeat
Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
-
C.
historicalJurisdiction
Indicates that one entity previously held legal or administrative authority over another entity during a past time period.
-
D.
hasHistoricTerritory
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c0a22881909eff0fc6c91a5f41 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.