Triple
T19735806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gronau |
E473976
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Gronau |
—
|
NE NERFINISHED |
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: Gronau | Statement: [Battle of Gronau, locatedIn, Gronau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gronau Context triple: [Battle of Gronau, locatedIn, Gronau]
-
A.
Gronau
chosen
Gronau is a town in Germany historically noted as the site of a battle during the Seven Years' War.
-
B.
Grotenberge
Grotenberge is a village in East Flanders, Belgium, that forms part of the municipality of Zottegem.
-
C.
Neudorf
Neudorf is a residential district of Strasbourg, France, known for its dense urban fabric, local commerce, and proximity to the city center.
-
D.
Neudorf
Neudorf is a village-level subdivision of the Tyrolean municipality of Umhausen in western Austria.
-
E.
Grüneberg
Grüneberg is a locality in Germany historically known as the site of the Battle of Grüneberg.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515ddea881909ea831b7bc16d934 |
completed | April 20, 2026, 4:16 p.m. |
Created at: April 10, 2026, 1:47 p.m.