Triple
T12179569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunshine Coast Line |
E290181
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Holland-on-Sea |
E290186
|
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: Holland-on-Sea | Statement: [Sunshine Coast Line, serves, Holland-on-Sea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holland-on-Sea Context triple: [Sunshine Coast Line, serves, Holland-on-Sea]
-
A.
Holland-on-Sea
chosen
Holland-on-Sea is a coastal town in Essex, England, known for its quiet residential character and sandy beaches along the North Sea.
-
B.
Veendam
Veendam is a town and municipality in the province of Groningen in the northeastern Netherlands, historically known for peat extraction and later for its industrial development.
-
C.
Londerzeel
Londerzeel is a municipality in the Flemish Brabant province of Belgium, known for its residential character and proximity to both Brussels and Antwerp.
-
D.
De Koog
De Koog is a coastal village and popular seaside resort on the Dutch Wadden Island of Texel, known for its beaches, dunes, and tourism.
-
E.
Eemshaven
Eemshaven is a major seaport and energy hub in the north of the Netherlands, known for its power plants, data centers, and offshore wind connections.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fc451c819086a2a97967b82908 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a88b8748190a6c95e143f370010 |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:50 p.m.