Triple
T6908765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurich district |
E159878
|
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: [Aurich district, capital, Aurich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aurich Context triple: [Aurich district, 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.
Itzehoe
Itzehoe is a historic town in northern Germany known for its medieval origins and role as a regional center in the state of Schleswig-Holstein.
-
C.
Elmshorn
Elmshorn is a town in northern Germany’s Schleswig-Holstein state, known as an industrial and commuter hub northwest of Hamburg.
-
D.
Husum
Husum is a small coastal town in northern Germany known for its North Sea harbor, maritime heritage, and role as a local cultural and commercial center.
-
E.
Delmenhorst
Delmenhorst is a mid-sized industrial and commuter city in northwestern Germany, located near Bremen in the federal state of Lower Saxony.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9be98748190b5cb698e66e3aa42 |
completed | March 27, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c75124cab88190a1510d77ed61c945 |
completed | March 28, 2026, 3:55 a.m. |
Created at: March 27, 2026, 2:25 p.m.