Triple
T15080383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiße Elster |
E380123
|
entity |
| Predicate | tributary |
P415
|
FINISHED |
| Object | Pleiße |
E889203
|
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: Pleiße | Statement: [Weiße Elster, tributary, Pleiße]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pleiße Context triple: [Weiße Elster, tributary, Pleiße]
-
A.
Pleiße
chosen
Pleiße is a river in eastern Germany that flows through the city of Leipzig and is a tributary of the White Elster.
-
B.
Seebruck
Seebruck is a Bavarian lakeside village and popular holiday resort on the northern shore of Lake Chiemsee in southern Germany.
-
C.
Ophasselt
Ophasselt is a village in the Flemish province of East Flanders, Belgium, known as one of the constituent communities of the city of Geraardsbergen.
-
D.
Wielenbach
Wielenbach is a small municipality in the Upper Bavarian region of Germany, situated within the district of Weilheim-Schongau.
-
E.
Seebach
Seebach is a quarter in the northern part of Zurich, Switzerland, known for its residential areas and proximity to major transport links.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff80008c88190840f94222f867478 |
completed | April 15, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae15d6308190a62b4f66c550db04 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:03 a.m.