Triple
T6712214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peacehaven |
E153171
|
entity |
| Predicate | liesWestOf |
P4239
|
FINISHED |
| Object | Newhaven |
E126840
|
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: Newhaven | Statement: [Peacehaven, liesWestOf, Newhaven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Newhaven Context triple: [Peacehaven, liesWestOf, Newhaven]
-
A.
Newhaven
Newhaven is a small coastal town on Phillip Island in Victoria, Australia, known as a gateway to the island and its popular tourist attractions.
-
B.
Newhaven
Newhaven is a historic coastal district of Edinburgh, Scotland, known for its former fishing village, harbor, and maritime heritage.
-
C.
Newhaven Harbour
Newhaven Harbour is a historic coastal harbour in Newhaven, East Sussex, England, serving as a key port and marina on the English Channel.
-
D.
Shoreham Port
Shoreham Port is a commercial seaport on the south coast of England that serves as an important hub for cargo handling, marine services, and local industry.
-
E.
Newhaven, England
chosen
Newhaven, England is a coastal town and ferry port in East Sussex, known historically as a Channel crossing point and for giving its name to New Haven, Connecticut.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d108acc08190b38b43161d8912b9 |
completed | March 27, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c700924fdc8190990187fbc1b3ab20 |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:07 p.m.