Triple
T35328636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berthold Kempinski |
E1020259
|
entity |
| Predicate | notableBusinessLocation |
P203901
|
FINISHED |
| Object | Leipziger Straße, Berlin |
E366945
|
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: Leipziger Straße, Berlin | Statement: [Berthold Kempinski, notableBusinessLocation, Leipziger Straße, Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBusinessLocation Context triple: [Berthold Kempinski, notableBusinessLocation, Leipziger Straße, Berlin]
-
A.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
D.
notableLocationOn
chosen
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
E.
notableBusinessType
Indicates that an entity is notably associated with, characterized by, or best known for a particular type of business.
- F. None of above.
Provenance (4 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3823c49bd481909b6101d34418b1b4 |
completed | June 21, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.