Triple
T34236846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitby (summer Saturdays, historically via Northern services) |
E878357
|
entity |
| Predicate | servedTownType |
P200597
|
FINISHED |
| Object | seaside resort |
—
|
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 | Statement: [Whitby (summer Saturdays, historically via Northern services), servedTownType, seaside resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedTownType Context triple: [Whitby (summer Saturdays, historically via Northern services), servedTownType, seaside resort]
-
A.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
-
B.
townServed
Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
-
C.
servesTownship
Indicates that an entity provides official services or administrative functions to a particular township.
-
D.
servedCity
Indicates that a service, route, or facility operates in, reaches, or is available to a particular city.
-
E.
associatedCityServed
Indicates that there is a relationship where a service, facility, or entity is linked to and serves a particular city.
- F. None of above. chosen
Provenance (4 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
| PDg | Predicate description generation | batch_69ff9a24996c8190ba2c5345d317cbdb |
completed | May 9, 2026, 8:33 p.m. |
Created at: May 1, 2026, 1:56 a.m.