Triple
T24752228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuiderzee |
E619174
|
entity |
| Predicate | historicalCityOnShore |
P99176
|
FINISHED |
| Object | Harderwijk |
—
|
NE NERFINISHED |
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: Harderwijk | Statement: [Zuiderzee, historicalCityOnShore, Harderwijk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCityOnShore Context triple: [Zuiderzee, historicalCityOnShore, Harderwijk]
-
A.
isHistoricPortOf
Indicates that a location served as a significant port for another place during a past historical period.
-
B.
isHistoricCoastalCity
chosen
Indicates that a city is both historically significant and located along a coast.
-
C.
cityDistrictOnShore
Indicates that a city district is located along or directly adjacent to the shore of a body of water.
-
D.
hasCityOnShore
Indicates that a city is located on or directly adjacent to the shore of a body of water.
-
E.
capitalCityLocatedOn
Indicates that a capital city is situated on or directly adjacent to a specific geographic feature, such as a river, coast, or lake.
- F. None of above.
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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 4:25 a.m.