Triple
T25091166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leyburn Rural District |
E628458
|
entity |
| Predicate | hasMarketTownInArea |
P130562
|
FINISHED |
| Object | Leyburn |
—
|
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: Leyburn | Statement: [Leyburn Rural District, hasMarketTownInArea, Leyburn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketTownInArea Context triple: [Leyburn Rural District, hasMarketTownInArea, Leyburn]
-
A.
containsMarketTown
chosen
Indicates that one region or area includes within its boundaries a town that functions as a market center.
-
B.
hasMarketTownStatus
Indicates that a settlement holds the official legal or historical status of being recognized as a market town.
-
C.
isInMarketTown
Indicates that an entity is located within or belongs to a town that functions as a local commercial or trading center.
-
D.
hasMarketTownHistory
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
E.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 18, 2026, 6:24 a.m.