Triple
T14561645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strasbourg bus network |
E341679
|
entity |
| Predicate | hasHub |
P2413
|
FINISHED |
| Object | La Wantzenau |
E1102459
|
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: La Wantzenau | Statement: [Strasbourg bus network, hasHub, La Wantzenau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: La Wantzenau Context triple: [Strasbourg bus network, hasHub, La Wantzenau]
-
A.
La Wantzenau
chosen
La Wantzenau is a commune in northeastern France, situated near Strasbourg in the Grand Est region and known for its riverside setting along the Ill and Rhine.
-
B.
Niederlahnstein
Niederlahnstein is a former town on the right bank of the Rhine in Rhineland-Palatinate, Germany, now part of the city of Lahnstein.
-
C.
Beutelsbach
Beutelsbach is a small municipality in the rural Passau district of Lower Bavaria in southeastern Germany.
-
D.
Lützel
Lützel is a district of the German city of Koblenz, located on the opposite bank of the Moselle River from the historic city center.
-
E.
Rolandseck
Rolandseck is a district of Remagen in Rhineland-Palatinate, Germany, known for its scenic location on the Rhine and its historic railway station and cultural venues.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb389d0f48190a1d9d69456d1cbe1 |
completed | April 14, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda9124af481908f43e3b541568e26 |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 10, 2026, 1:23 a.m.