Triple
T1546975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Frisia |
E32998
|
entity |
| Predicate | largestCity |
P235
|
FINISHED |
| Object | Emden |
E29348
|
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: Emden | Statement: [East Frisia, largestCity, Emden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emden Context triple: [East Frisia, largestCity, Emden]
-
A.
Emden
chosen
Emden is a historic port city in northwestern Germany known for its maritime industry and location near the North Sea.
-
B.
Kolberg
Kolberg is a historic Baltic Sea port city in present-day Kołobrzeg, Poland, known for its strategic military importance and spa tourism.
-
C.
Bismarck
Bismarck is a mid-sized city in south-central North Dakota that serves as the state’s political and administrative center.
-
D.
Bismarck
Bismarck was a famous German World War II battleship renowned for its powerful armament, heavy armor, and dramatic sinking after a major North Atlantic pursuit.
-
E.
Kronstadt
Kronstadt is a historic Russian naval port and fortress city located on Kotlin Island near Saint Petersburg, long serving as a key base for the Russian Baltic Fleet.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb20dd5a88190b3d6e6f0004fe9b4 |
completed | March 7, 2026, 5:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad37092b648190a339114ffc37d1db |
completed | March 8, 2026, 8:44 a.m. |
Created at: March 4, 2026, 7:26 p.m.