Triple
T20791275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Shropshire |
E511782
|
entity |
| Predicate | hasMajorSettlementType |
P115593
|
FINISHED |
| Object | market town |
—
|
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: market town | Statement: [North Shropshire, hasMajorSettlementType, market town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorSettlementType Context triple: [North Shropshire, hasMajorSettlementType, market town]
-
A.
hasMajorSettlementsType
chosen
Indicates that an entity is associated with major settlements of a specified type (e.g., cities, towns, villages).
-
B.
hasMajorSettlementRegion
Indicates that a major settlement is located within or primarily associated with a particular geographic region.
-
C.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
D.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
E.
hasCityStatusSettlement
Indicates that a settlement possesses official recognition or designation as a city.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c29010508190bf2cf577d7f64754 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.