Triple
T8439312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhine-Ruhr metropolitan region |
E199309
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Pulheim |
E598842
|
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: Pulheim | Statement: [Rhine-Ruhr metropolitan region, containsCity, Pulheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pulheim Context triple: [Rhine-Ruhr metropolitan region, containsCity, Pulheim]
-
A.
Pulheim
chosen
Pulheim is a town in western Germany’s North Rhine-Westphalia, situated just northwest of Cologne within the broader Cologne/Bonn urban area.
-
B.
Meerbusch
Meerbusch is a town in the German state of North Rhine-Westphalia, situated on the west bank of the Rhine near Düsseldorf and known for its affluent residential areas and green surroundings.
-
C.
Sulzheim
Sulzheim is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
-
D.
Riehe
Riehe is a small river in Lower Saxony, Germany, known as one of the tributaries feeding into the Innerste.
-
E.
Walldorf
Walldorf is a town in southwestern Germany best known as the headquarters of software giant SAP and for its strong economic base in the technology sector.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe13708988190a534e38d8254c9bd |
completed | March 31, 2026, 2:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc1b1c21c8190969446fb6fd0394f |
completed | April 3, 2026, 1:33 p.m. |
Created at: March 30, 2026, 6:08 p.m.