Triple
T9942339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmersdorf |
E194112
|
entity |
| Predicate | publicTransport |
P1288
|
FINISHED |
| Object |
U9 line
The U9 line is a major Berlin U-Bahn subway route running north–south through the city and serving districts such as Wilmersdorf.
|
E830729
|
NE FINISHED |
How this triple was built (4 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: U9 line | Statement: [Wilmersdorf, publicTransport, U9 line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U9 line Context triple: [Wilmersdorf, publicTransport, U9 line]
-
A.
U7 line
The U7 line is a route of the Frankfurt U-Bahn rapid transit system that runs across the city and serves major central stations including Hauptwache.
-
B.
U5 line
The U5 line is a major Berlin U-Bahn route running east–west that connects central hubs like Alexanderplatz with eastern districts of the city.
-
C.
U1 line
The U1 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with several northern suburbs.
-
D.
U6 line
The U6 line is a route of the Frankfurt U-Bahn rapid transit system that connects various districts across the city, including central hubs such as Hauptwache.
-
E.
U3 line
The U3 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with its northwestern suburbs.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: U9 line Triple: [Wilmersdorf, publicTransport, U9 line]
Generated description
The U9 line is a major Berlin U-Bahn subway route running north–south through the city and serving districts such as Wilmersdorf.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: U9 line Target entity description: The U9 line is a major Berlin U-Bahn subway route running north–south through the city and serving districts such as Wilmersdorf.
-
A.
U7 line
The U7 line is a route of the Frankfurt U-Bahn rapid transit system that runs across the city and serves major central stations including Hauptwache.
-
B.
U5 line
The U5 line is a major Berlin U-Bahn route running east–west that connects central hubs like Alexanderplatz with eastern districts of the city.
-
C.
U1 line
The U1 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with several northern suburbs.
-
D.
U6 line
The U6 line is a route of the Frankfurt U-Bahn rapid transit system that connects various districts across the city, including central hubs such as Hauptwache.
-
E.
U3 line
The U3 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with its northwestern suburbs.
- F. None of above. chosen
Provenance (5 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6124a188190b41feadb7b2f8922 |
completed | April 2, 2026, 12:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d22911a9ac81909caa2afb30e4860b |
completed | April 5, 2026, 9:19 a.m. |
| NEDg | Description generation | batch_69d22ad44b748190a774a2b2f8d5fabf |
completed | April 5, 2026, 9:26 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d22b37ce8481909a52a144605d44a4 |
completed | April 5, 2026, 9:28 a.m. |
Created at: March 30, 2026, 8:45 p.m.