Triple
T221763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Yarmouth |
E4228
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object |
Wellington Pier
Wellington Pier is a historic seaside pleasure pier and entertainment venue located on the seafront of Great Yarmouth, England.
|
E29023
|
NE FINISHED |
How this triple was built (4 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: Wellington Pier | Statement: [Great Yarmouth, hasLandmark, Wellington Pier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wellington Pier Context triple: [Great Yarmouth, hasLandmark, Wellington Pier]
-
A.
Hyde Street Pier
Hyde Street Pier is a historic San Francisco waterfront pier that serves as part of the San Francisco Maritime National Historical Park, featuring preserved ships and maritime exhibits.
-
B.
Bennelong Point
Bennelong Point is a prominent headland on Sydney Harbour that forms the site of the iconic Sydney Opera House.
-
C.
Wellington Bridge
Wellington Bridge is a roadway bridge in the Boston area that carries traffic across the Mystic River between Medford and Somerville, Massachusetts.
-
D.
Pier
Pier is a given name, commonly used in various European countries, that is derived from the name Pierre or Peter.
-
E.
Buckhaven
Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Wellington Pier Triple: [Great Yarmouth, hasLandmark, Wellington Pier]
Generated description
Wellington Pier is a historic seaside pleasure pier and entertainment venue located on the seafront of Great Yarmouth, England.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Wellington Pier Target entity description: Wellington Pier is a historic seaside pleasure pier and entertainment venue located on the seafront of Great Yarmouth, England.
-
A.
Hyde Street Pier
Hyde Street Pier is a historic San Francisco waterfront pier that serves as part of the San Francisco Maritime National Historical Park, featuring preserved ships and maritime exhibits.
-
B.
Bennelong Point
Bennelong Point is a prominent headland on Sydney Harbour that forms the site of the iconic Sydney Opera House.
-
C.
Wellington Bridge
Wellington Bridge is a roadway bridge in the Boston area that carries traffic across the Mystic River between Medford and Somerville, Massachusetts.
-
D.
Pier
Pier is a given name, commonly used in various European countries, that is derived from the name Pierre or Peter.
-
E.
Buckhaven
Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
- F. None of above. chosen
Provenance (5 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c6e6fbc8190a8744e193df513e8 |
completed | Feb. 28, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a358799c04819099e9795809236b31 |
completed | Feb. 28, 2026, 9:04 p.m. |
| NEDg | Description generation | batch_69a35a2255488190928a737da885545c |
completed | Feb. 28, 2026, 9:12 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69a35a76e5988190b40d83367feece15 |
completed | Feb. 28, 2026, 9:13 p.m. |
Created at: Feb. 28, 2026, 2:53 a.m.