Triple
T28874055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Pier |
E732215
|
entity |
| Predicate | isSeasidePier |
P165687
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [North Pier, isSeasidePier, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeasidePier Context triple: [North Pier, isSeasidePier, true]
-
A.
isSeasideVillage
Indicates that a village is located directly by the sea or coastline.
-
B.
isSeasideVenue
Indicates that a venue is located by the sea or coastline, typically offering direct proximity or access to the seaside.
-
C.
isSeasideResort
Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
-
D.
isSeasideCounterpartOf
Indicates that one entity serves as the seaside equivalent or corresponding version of another entity.
-
E.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4a48888190b3c1bc721712ae71 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 7:36 a.m.