Triple
T22383629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siebengebirge |
E553337
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Lohrberg |
—
|
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: Lohrberg | Statement: [Siebengebirge, contains, Lohrberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lohrberg Context triple: [Siebengebirge, contains, Lohrberg]
-
A.
Lohrberg
chosen
Lohrberg is a hill in Germany’s Siebengebirge range, known for its forested slopes and scenic hiking paths overlooking the Rhine valley.
-
B.
Lohrberg
Lohrberg is a hill and popular recreational area in Frankfurt am Main, known for its vineyards, panoramic city views, and green spaces.
-
C.
Lohberg
Lohberg is a small Bavarian village in the Bavarian Forest region of Germany, known as a gateway to outdoor activities around the Großer Arber mountain.
-
D.
Mahlberg
Mahlberg is a small town and municipality in the Ortenau district of Baden-Württemberg in southwestern Germany.
-
E.
Loeher
Loeher is a surname that serves as an alternative spelling variant of the name Loehr.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582d8e548190a7330de49d519675 |
completed | April 29, 2026, 1 a.m. |
Created at: April 16, 2026, 8:45 p.m.