Triple
T14367574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lauffeld |
E356274
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Lauffeld |
E356274
|
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: Lauffeld | Statement: [Battle of Lauffeld, locatedIn, Lauffeld]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lauffeld Context triple: [Battle of Lauffeld, locatedIn, Lauffeld]
-
A.
Lauffeld
chosen
Lauffeld is a village in present-day Belgium best known as the site of the 1747 Battle of Lauffeld during the War of the Austrian Succession.
-
B.
Lülsfeld
Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
-
C.
Erstfeld
Erstfeld is a municipality in the Swiss canton of Uri, situated in a mountainous valley that serves as an important transport corridor through the Alps.
-
D.
Hasselfelde
Hasselfelde is a small town in the Harz region of central Germany, now incorporated into the municipality of Oberharz am Brocken.
-
E.
Hellefeld
Hellefeld is a village and district within the town of Sundern in the Hochsauerland region of North Rhine-Westphalia, Germany.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8faf00e8819087d7100e9d8c1877 |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c2a938081909ccd9fe7c5021dc6 |
completed | May 9, 2026, 3 p.m. |
Created at: April 10, 2026, 1:15 a.m.