Triple
T22218359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kottbusser Tor station |
E549136
|
entity |
| Predicate | isLocatedInAreaKnownFor |
P120961
|
FINISHED |
| Object | nightlife |
—
|
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: nightlife | Statement: [Kottbusser Tor station, isLocatedInAreaKnownFor, nightlife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInAreaKnownFor Context triple: [Kottbusser Tor station, isLocatedInAreaKnownFor, nightlife]
-
A.
isLocatedInDistrictKnownFor
chosen
Indicates that an entity is situated within a district that is notably recognized for a particular characteristic, feature, or reputation.
-
B.
connectsToAreaKnownFor
Indicates that something has a direct link or association to a specific area that is recognized or notable for certain characteristics or features.
-
C.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
D.
governsAreaKnownFor
Indicates that a governing entity exercises authority over an area that is notably recognized for a particular characteristic, feature, or attribute.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8ddb448190a45f0418d813afd0 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.