Triple
T16155727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral Hipper |
E392035
|
entity |
| Predicate | homePort |
P3150
|
FINISHED |
| Object | Wilhelmshaven |
E41561
|
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: Wilhelmshaven | Statement: [Admiral Hipper, homePort, Wilhelmshaven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wilhelmshaven Context triple: [Admiral Hipper, homePort, Wilhelmshaven]
-
A.
Wilhelmshaven
chosen
Wilhelmshaven is a coastal city in northwestern Germany known for its major naval base and port on the North Sea.
-
B.
Cuxhaven
Cuxhaven is a German port city on the North Sea coast that historically served as an important naval and maritime hub.
-
C.
Dover
Dover is a residential and educational neighborhood in western Singapore, known for its proximity to universities and polytechnics.
-
D.
Dover
Dover is a small town in eastern Dutchess County, New York, known for its rural character and location near the Connecticut border.
-
E.
Dover
Dover is the capital city of the U.S. state of Delaware, known for its historic district, government institutions, and proximity to Delaware Bay.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e5aa57c8190a9d89dd57e30318f |
completed | April 17, 2026, 11:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff7ae46dc81908cba9152a6080c3a |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 5:01 a.m.