Triple
T16786997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mablethorpe and Sutton Urban District |
E408004
|
entity |
| Predicate | administeredTypeOfArea |
P6822
|
FINISHED |
| Object | seaside resort towns |
—
|
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: seaside resort towns | Statement: [Mablethorpe and Sutton Urban District, administeredTypeOfArea, seaside resort towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administeredTypeOfArea Context triple: [Mablethorpe and Sutton Urban District, administeredTypeOfArea, seaside resort towns]
-
A.
typeOfAdministration
Indicates the specific form or system of administration applied to or governing an entity.
-
B.
typeOfAreaRepresented
Indicates that one entity specifies the kind or category of area that another entity represents.
-
C.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
D.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
E.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21b6a408190b0766138cc9a9ee2 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.