Triple
T1546974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Frisia |
E32998
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Aurich |
E208915
|
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: Aurich | Statement: [East Frisia, capital, Aurich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aurich Context triple: [East Frisia, capital, Aurich]
-
A.
Aurich
chosen
Aurich is a historic town in northwestern Germany that serves as one of the principal urban centers of the East Frisia region in Lower Saxony.
-
B.
Elmshorn
Elmshorn is a town in northern Germany’s Schleswig-Holstein state, known as an industrial and commuter hub northwest of Hamburg.
-
C.
Delmenhorst
Delmenhorst is a mid-sized industrial and commuter city in northwestern Germany, located near Bremen in the federal state of Lower Saxony.
-
D.
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.
-
E.
Soest
Soest is a historic town in North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and former significance as a Hanseatic trading center.
- 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_69addf2ab134819090727cc68ff5c02e |
completed | March 8, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:26 p.m.