Triple
T3102906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deal, Kent |
E64760
|
entity |
| Predicate | hasStructure |
P35
|
FINISHED |
| Object | Deal Pier |
E212139
|
NE 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: Deal Pier | Statement: [Deal, Kent, hasStructure, Deal Pier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deal Pier Context triple: [Deal, Kent, hasStructure, Deal Pier]
-
A.
Deal Pier
chosen
Deal Pier is a historic pleasure pier extending into the English Channel from the seaside town of Deal in Kent, England.
-
B.
Battery Pier
Battery Pier is a harbour pier located in Douglas, Isle of Man, serving as part of the town’s maritime infrastructure.
-
C.
G Pier
G Pier is one of the passenger boarding concourses at Amsterdam Airport Schiphol, serving multiple gates for international flights.
-
D.
H Pier
H Pier is one of the passenger boarding concourses at Amsterdam Airport Schiphol, serving multiple gates for international flights.
-
E.
Pier B
Pier B is one of the main passenger boarding concourses at Brussels Airport, primarily serving non-Schengen and long-haul international flights.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26df128819086541db7680c8c24 |
completed | March 8, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f5994088190abc4b56040922c16 |
completed | March 12, 2026, 12:56 a.m. |
Created at: March 8, 2026, 3:03 p.m.