Triple
T11803046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jemmingen |
E280675
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Jemgum |
E666412
|
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: Jemgum | Statement: [Battle of Jemmingen, location, Jemgum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jemgum Context triple: [Battle of Jemmingen, location, Jemgum]
-
A.
Jemgum
chosen
Jemgum is a small municipality in the East Frisian region of Lower Saxony in northwestern Germany, known for its rural landscape along the Ems River.
-
B.
Junggumun
Junggumun is a historical writing system used in Korea that incorporated Chinese characters to represent Korean grammatical elements and sounds.
-
C.
Gimje
Gimje is a city in North Jeolla Province, South Korea, known for its expansive plains and agricultural production, particularly rice.
-
D.
Jangsaengpo
Jangsaengpo is a coastal district in Ulsan, South Korea, historically known as a major whaling port and now a center for marine and whale-related tourism.
-
E.
Munji
Munji is a lesser-known Eastern Iranian language spoken by the Munji people in the remote Munjan Valley of northeastern Afghanistan.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a5a2048190b68027f622366079 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f1314300248190847b9c61bbfda121 |
completed | April 28, 2026, 10:14 p.m. |
Created at: April 8, 2026, 9:42 p.m.