Triple
T29207625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig Hbf |
E740457
|
entity |
| Predicate | hasShoppingCentreName |
P33146
|
FINISHED |
| Object | Promenaden Hauptbahnhof Leipzig |
—
|
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: Promenaden Hauptbahnhof Leipzig | Statement: [Leipzig Hbf, hasShoppingCentreName, Promenaden Hauptbahnhof Leipzig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoppingCentreName Context triple: [Leipzig Hbf, hasShoppingCentreName, Promenaden Hauptbahnhof Leipzig]
-
A.
hasShoppingMallName
chosen
Indicates that an entity (such as a shopping mall) is associated with or identified by a specific name.
-
B.
hasShoppingDistrictName
Indicates that an entity’s shopping district is identified by a specific name.
-
C.
locationOfShoppingCenter
Indicates that a specified place is the geographic location where a particular shopping center is situated.
-
D.
hasShoppingDistrict
Indicates that a place contains or is associated with a designated area where multiple shops and commercial retail activities are concentrated.
-
E.
shoppingCenterInstanceOf
Indicates that a specific shopping center is an instance of a particular type or class of shopping centers.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 12:10 p.m.