Triple
T3900157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langwasser depot |
E90467
|
entity |
| Predicate | locatedInDistrict |
P40
|
FINISHED |
| Object | Langwasser |
E398164
|
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: Langwasser | Statement: [Langwasser depot, locatedInDistrict, Langwasser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langwasser Context triple: [Langwasser depot, locatedInDistrict, Langwasser]
-
A.
Langwasser
chosen
Langwasser is a residential district in the southeast of Nuremberg, Germany, known for its post-war urban planning and large housing estates.
-
B.
Langwasser Süd
Langwasser Süd is a southern district station in Nuremberg, Germany, serving as a key terminus on the city’s U-Bahn rapid transit network.
-
C.
Wrey
Wrey is a variant spelling of the surname Wray, which is of English origin.
-
D.
Wickwar
Wickwar is a small historic village and civil parish in South Gloucestershire, England, known for its traditional architecture and rural surroundings.
-
E.
Aywick
Aywick is a small coastal settlement on the island of Yell in Shetland, Scotland.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecf17ef4819083db0a22e24d5b89 |
completed | March 9, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5285093208190a2ba00afcbd8a261 |
completed | March 14, 2026, 9:20 a.m. |
Created at: March 9, 2026, 3:21 p.m.