Triple
T27174573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernauer Straße |
E683006
|
entity |
| Predicate | cityQuarterBorder |
P115250
|
FINISHED |
| Object | Gesundbrunnen |
—
|
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: Gesundbrunnen | Statement: [Bernauer Straße, cityQuarterBorder, Gesundbrunnen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityQuarterBorder Context triple: [Bernauer Straße, cityQuarterBorder, Gesundbrunnen]
-
A.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
B.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
C.
borderSectionOf
chosen
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
D.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- F. None of above.
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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6254a0a9c8190a5491c785635ca35 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:25 a.m.