Triple
T7979219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pischa |
E185522
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Davos Platz |
E101887
|
NE 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: Davos Platz | Statement: [Pischa, near, Davos Platz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Davos Platz Context triple: [Pischa, near, Davos Platz]
-
A.
Davos Platz
chosen
Davos Platz is the central district of the Swiss Alpine town of Davos, known for hosting major international events and serving as a key hub for tourism and winter sports.
-
B.
Innsbrucker Platz
Innsbrucker Platz is a public square in Berlin, Germany, known as a local traffic and transport hub in the Schöneberg district.
-
C.
Opernplatz
Opernplatz is a prominent public square in central Frankfurt am Main, Germany, known especially for hosting the historic Alte Oper concert hall.
-
D.
Schlossplatz
Schlossplatz is a historic central square in Berlin that once fronted the Berlin City Palace and now serves as the site of the reconstructed Humboldt Forum.
-
E.
Rathenauplatz
Rathenauplatz is an underground rapid transit station in Nuremberg, Germany, serving as part of the city’s U-Bahn network.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c261904819086910898071f3629 |
completed | March 31, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe0d3c724819087df03cea2ed998f |
completed | March 31, 2026, 2:57 p.m. |
Created at: March 30, 2026, 5:14 p.m.