Triple
T37811908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mar |
E942667
|
entity |
| Predicate | historicalCountyAreaOf |
—
|
GENERATED |
| Object | Aberdeenshire |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCountyAreaOf Context triple: [Mar, historicalCountyAreaOf, Aberdeenshire]
-
A.
historicalCountyArea
chosen
Indicates that an entity’s area measurement corresponds to the size of a county as it existed during a specified historical period.
-
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.
historicalEstateAreaFor
Indicates that a specified area value represents the historical estate area associated with a given entity.
-
D.
historicalCountyChange
Indicates that a county’s administrative boundaries or status have been altered over time, such as through creation, dissolution, merger, or territorial reassignment.
-
E.
hasHistoricCountyCode
Indicates that an entity is associated with a specific historic county, identified by its county code.
- F. None of above.
Provenance (1 batch)
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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.