Triple
T16793772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet Adenauer II |
E408178
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Bonn |
E23133
|
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: Bonn | Statement: [Cabinet Adenauer II, capital, Bonn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bonn Context triple: [Cabinet Adenauer II, capital, Bonn]
-
A.
Bonn
chosen
Bonn is a historic German city on the Rhine River, best known for being the birthplace of Ludwig van Beethoven and the former seat of the federal government before reunification.
-
B.
Cologne
Cologne is an unincorporated community within Galloway Township in Atlantic County, New Jersey, known primarily as a small residential area in the region.
-
C.
Cologne
Cologne is a historic German city on the Rhine River, renowned for its Gothic cathedral, vibrant cultural scene, and status as a major economic and media hub.
-
D.
Düsseldorf
Düsseldorf is a major German city on the Rhine River known for its fashion and art scenes, modern architecture, and status as an important economic and financial center.
-
E.
Bonn-Duisdorf
Bonn-Duisdorf is a district in the western part of Bonn, Germany, characterized by residential areas and local commercial infrastructure.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a8b66c8190b83d8af85d2b23a8 |
completed | April 18, 2026, 4:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c3489848190869bebedcb5c0564 |
completed | May 11, 2026, 7:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.