Triple
T27868117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardale |
E704411
|
entity |
| Predicate | historicalCountyTownNearby |
P115180
|
FINISHED |
| Object | Appleby-in-Westmorland |
—
|
NE NERFINISHED |
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: Appleby-in-Westmorland | Statement: [Mardale, historicalCountyTownNearby, Appleby-in-Westmorland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCountyTownNearby Context triple: [Mardale, historicalCountyTownNearby, Appleby-in-Westmorland]
-
A.
hasHistoricCountyTownRelation
chosen
Indicates a relationship where a town serves or has served as the historic county town (traditional administrative center) of a given county.
-
B.
historicalTownshipOf
Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
-
C.
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.
-
D.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
E.
nearbyTownFormerName
Indicates that the nearby town previously had a different name, specifying its former name in relation to the current nearby town.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 27, 2026, 6:22 p.m.