Triple
T7703805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mühlenstrasse |
E174562
|
entity |
| Predicate | hasContemporaryUse |
P34114
|
FINISHED |
| Object | site for cultural events and street art viewing |
—
|
LITERAL 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: site for cultural events and street art viewing | Statement: [Mühlenstrasse, hasContemporaryUse, site for cultural events and street art viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemporaryUse Context triple: [Mühlenstrasse, hasContemporaryUse, site for cultural events and street art viewing]
-
A.
contemporaryUse
chosen
Indicates that something is currently used or practiced in the present time or modern context.
-
B.
hasContemporaryRecognition
Indicates that an entity is currently acknowledged, honored, or widely recognized in the present time or modern era.
-
C.
hasContemporaryActivity
Indicates that two activities occur during the same time period or overlap in time.
-
D.
modernUse
Indicates how something is currently used or applied in modern times.
-
E.
hasModernSiteUse
Indicates that an entity is currently used or functions in a particular way at a modern site or location.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.