Triple
T12035490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Służew metro station |
E286526
|
entity |
| Predicate | servesNeighbourhood |
P82
|
FINISHED |
| Object | Służew |
E994158
|
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: Służew | Statement: [Służew metro station, servesNeighbourhood, Służew]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Służew Context triple: [Służew metro station, servesNeighbourhood, Służew]
-
A.
Służew
chosen
Służew is a residential neighborhood in the Mokotów district of Warsaw, Poland, known for its housing estates, green areas, and convenient access to the city center via the metro.
-
B.
Służewiec
Służewiec is a district in Warsaw, Poland, known for its business centers, residential areas, and the historic Służewiec Horse Race Track.
-
C.
Słupia
Słupia is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
D.
Supraśl
Supraśl is a small historic spa town in northeastern Poland, known for its Orthodox monastery complex and picturesque setting along the Supraśl River.
-
E.
Trzciana
Trzciana is a village in southern Poland historically notable as the site of the 1629 Battle of Trzciana during the Polish–Swedish War.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90408cbf0819093270c9833ef149a |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6717c2d848190b702470e6bcead2d |
completed | May 2, 2026, 9:49 p.m. |
Created at: April 8, 2026, 9:47 p.m.