Triple
T1756348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Germany |
E38556
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Port of Bremen |
E76455
|
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: Port of Bremen | Statement: [Northern Germany, hasPort, Port of Bremen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Port of Bremen Context triple: [Northern Germany, hasPort, Port of Bremen]
-
A.
Port of Hamburg
The Port of Hamburg is Germany’s largest seaport and a major European logistics hub, known as the country’s “Gateway to the World.”
-
B.
Bremerhaven
Bremerhaven is a major German port city on the North Sea, known for its maritime industry, shipbuilding, and role as a key hub for trade and logistics.
-
C.
Bremen
chosen
Bremen is a city-state in northwestern Germany comprising the cities of Bremen and Bremerhaven, known for its historic Hanseatic heritage and major port on the Weser River.
-
D.
Hamburg
Hamburg is Germany’s second-largest city and a major northern European port and cultural center on the River Elbe.
-
E.
Port of Holland
Port of Holland is a commercial and industrial harbor facility in Holland, Michigan, serving as a key shipping and logistics hub for the West Michigan region.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa643b623081908064be75758ec5de |
completed | March 6, 2026, 5:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adb5c4f7cc8190a60d3bd276711b27 |
completed | March 8, 2026, 5:45 p.m. |
Created at: March 4, 2026, 7:31 p.m.