Triple
T22309102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurfürstendamm station |
E551464
|
entity |
| Predicate | hasNetworkMapSymbolLocation |
P30881
|
FINISHED |
| Object | Berlin U-Bahn network map |
—
|
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: Berlin U-Bahn network map | Statement: [Kurfürstendamm station, hasNetworkMapSymbolLocation, Berlin U-Bahn network map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkMapSymbolLocation Context triple: [Kurfürstendamm station, hasNetworkMapSymbolLocation, Berlin U-Bahn network map]
-
A.
hasSymbolLocation
chosen
Indicates that a symbol is associated with or positioned at a specific location.
-
B.
isOnSystemMap
Indicates that an entity is currently displayed or represented on a particular system map.
-
C.
hasMapframe
Indicates that an entity is associated with an embedded, interactive map frame representation of its geographic location or area.
-
D.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
E.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574c8a248190bf5eef5be78381fd |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.