Triple
T9462618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barmen Declaration |
E228186
|
entity |
| Predicate | placeOfOrigin |
P3743
|
FINISHED |
| Object | Barmen |
E54311
|
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: Barmen | Statement: [Barmen Declaration, placeOfOrigin, Barmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barmen Context triple: [Barmen Declaration, placeOfOrigin, Barmen]
-
A.
Barmen
chosen
Barmen is a historic industrial district in the German city of Wuppertal, known as a former textile and manufacturing center in the Ruhr region.
-
B.
Bornheim
Bornheim is a lively residential and nightlife district in Frankfurt am Main, Germany, known for its traditional cider taverns, historic streets, and vibrant local culture.
-
C.
Barmer
Barmer is a prominent city in the western Indian state of Rajasthan, known for its desert landscape, handicrafts, and proximity to the Thar Desert.
-
D.
Borken
Borken is a town in western Germany that serves as an administrative and commercial center in the state of North Rhine-Westphalia.
-
E.
Baar-Ebenhausen
Baar-Ebenhausen is a Bavarian municipality in southern Germany known for its residential character and location along the Ilm River.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcd9794819093c392489d4efbe9 |
completed | April 1, 2026, 8:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d122a75aa08190adfe03d9f785f1ff |
completed | April 4, 2026, 2:39 p.m. |
Created at: March 30, 2026, 7:53 p.m.