Triple
T22183758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Favoriten |
E548236
|
entity |
| Predicate | hasNeighbouringDistrict |
P17964
|
FINISHED |
| Object | Liesing |
—
|
NE NERFINISHED |
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: Liesing | Statement: [Favoriten, hasNeighbouringDistrict, Liesing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liesing Context triple: [Favoriten, hasNeighbouringDistrict, Liesing]
-
A.
Liesing
chosen
Liesing is the 23rd and southernmost district of Vienna, Austria, known for its mix of residential areas, industrial zones, and green spaces along the Liesingbach stream.
-
B.
Liesing (Mur)
Liesing (Mur) is a small river in Styria, Austria, that flows through the Graz area before joining the Mur River.
-
C.
Lainsitz
Lainsitz is the German name for the Lužnice River, a waterway flowing through the Czech Republic and Austria.
-
D.
Essling
Essling is a village near Vienna, Austria, historically notable as one of the sites of the 1809 Battle of Aspern-Essling during the Napoleonic Wars.
-
E.
Leissigen
Leissigen is a Swiss village in the canton of Bern, known for its scenic location in the Bernese Oberland on the shores of Lake Thun.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa75440819084cbe9176b9edb47 |
completed | April 28, 2026, 9:46 p.m. |
Created at: April 16, 2026, 8:35 p.m.