Triple
T14150932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roxburghshire |
E350674
|
entity |
| Predicate | hasHistoricRegionType |
P55801
|
FINISHED |
| Object | Border county |
—
|
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: Border county | Statement: [Roxburghshire, hasHistoricRegionType, Border county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricRegionType Context triple: [Roxburghshire, hasHistoricRegionType, Border county]
-
A.
hasHistoricRegionStyle
Indicates that an entity exhibits or is characterized by the architectural or cultural style associated with a particular historic region.
-
B.
isInHistoricRegion
chosen
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
C.
hasHistoricResourceType
Indicates that an entity is associated with a particular category or type of historic resource.
-
D.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
E.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6124e23481909e5132a40a1d8624 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:57 a.m.