Triple
T20317718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furieade maritime festival |
E510420
|
entity |
| Predicate | organisedIn |
P8619
|
FINISHED |
| Object | Maassluis harbour area |
—
|
NE NERFINISHED |
How this triple was built (3 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: Maassluis harbour area | Statement: [Furieade maritime festival, organisedIn, Maassluis harbour area]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maassluis harbour area Context triple: [Furieade maritime festival, organisedIn, Maassluis harbour area]
-
A.
Oud-Beijerland harbour
Oud-Beijerland harbour is a small Dutch riverside port serving the town of Oud-Beijerland, historically used for local trade, fishing, and recreational boating.
-
B.
Maasbracht harbor
Maasbracht harbor is a major inland port in the Netherlands that serves as an important logistics and transshipment hub on the River Meuse and the Dutch canal network.
-
C.
Middelburg harbour
Middelburg harbour is the historic port area of Middelburg in the Netherlands, serving as the central hub for maritime activity and connecting the city’s canal network to larger waterways.
-
D.
Numansdorp harbor
Numansdorp harbor is a small local port in the village of Numansdorp in South Holland, the Netherlands, serving mainly recreational boating and small-scale maritime activities.
-
E.
Werkendam harbor
Werkendam harbor is a Dutch inland port and marina on the River Merwede that serves as a regional hub for river shipping, shipbuilding, and water-related industries in the town of Werkendam.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Maassluis harbour area Target entity description: Maassluis harbour area is a historic port district in the Dutch town of Maassluis, known for its maritime heritage, classic ships, and waterfront events.
-
A.
Oud-Beijerland harbour
Oud-Beijerland harbour is a small Dutch riverside port serving the town of Oud-Beijerland, historically used for local trade, fishing, and recreational boating.
-
B.
Maasbracht harbor
Maasbracht harbor is a major inland port in the Netherlands that serves as an important logistics and transshipment hub on the River Meuse and the Dutch canal network.
-
C.
Middelburg harbour
Middelburg harbour is the historic port area of Middelburg in the Netherlands, serving as the central hub for maritime activity and connecting the city’s canal network to larger waterways.
-
D.
Numansdorp harbor
Numansdorp harbor is a small local port in the village of Numansdorp in South Holland, the Netherlands, serving mainly recreational boating and small-scale maritime activities.
-
E.
Werkendam harbor
Werkendam harbor is a Dutch inland port and marina on the River Merwede that serves as a regional hub for river shipping, shipbuilding, and water-related industries in the town of Werkendam.
- F. None of above. chosen
Provenance (2 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67788ca3c8190a3496fd54a5870d6 |
completed | April 20, 2026, 6:59 p.m. |
Created at: April 16, 2026, 11:19 a.m.