Triple
T15070296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | light cruiser Emden |
E379857
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | city of Emden |
E605282
|
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: city of Emden | Statement: [light cruiser Emden, namedAfter, city of Emden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Emden Context triple: [light cruiser Emden, namedAfter, city of Emden]
-
A.
city of Emden
chosen
The city of Emden is a historic seaport and independent city in northwestern Germany, located in East Frisia on the North Sea coast.
-
B.
Emder Hafen
Emder Hafen is the historic seaport of the city of Emden in northwestern Germany, serving as an important maritime and commercial hub on the North Sea coast.
-
C.
City of Wesel
The City of Wesel is a historic German town on the Lower Rhine that became an important Reformation and trading center in the early modern period.
-
D.
Friedeburg
Friedeburg is a small municipality in Lower Saxony, Germany, known for its rural character and location within the East Frisian region.
-
E.
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.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7f86df48190b3a2cf441fefb477 |
completed | April 15, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5cd4b6c8190aa9ff73d5be31864 |
completed | May 9, 2026, 3:11 a.m. |
Created at: April 10, 2026, 3:02 a.m.