Triple
T15097468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luisenplatz (Potsdam) |
E360576
|
entity |
| Predicate | isGatewayAreaTo |
P42057
|
FINISHED |
| Object | historic center of Potsdam |
—
|
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: historic center of Potsdam | Statement: [Luisenplatz (Potsdam), isGatewayAreaTo, historic center of Potsdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGatewayAreaTo Context triple: [Luisenplatz (Potsdam), isGatewayAreaTo, historic center of Potsdam]
-
A.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
B.
isGatewayCommunityFor
chosen
Indicates that one community serves as an entry point, access hub, or primary connection for another community or larger region.
-
C.
hasGatewayCity
Indicates that one place serves as the primary gateway city (main entry or transit hub) for accessing another place.
-
D.
hasAreaNumber
Indicates that an entity is associated with a specific area identified by a numerical code.
-
E.
hasAreaCode
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005466e9c8190a68e1fbeb8922b1a |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.