Triple
T14057502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC Strasbourg Alsace |
E338255
|
entity |
| Predicate | foundedAs |
P364
|
FINISHED |
| Object | Neudorf |
E355771
|
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: Neudorf | Statement: [RC Strasbourg Alsace, foundedAs, Neudorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neudorf Context triple: [RC Strasbourg Alsace, foundedAs, Neudorf]
-
A.
Neudorf
chosen
Neudorf is a residential district of Strasbourg, France, known for its dense urban fabric, local commerce, and proximity to the city center.
-
B.
Neuendorf
Neuendorf is a small village on the Baltic Sea island of Hiddensee in Germany, known for its traditional thatched houses and maritime character.
-
C.
Nordendorf
Nordendorf is a small municipality in Bavaria, Germany, situated within the Augsburg district.
-
D.
Nauendorf
Nauendorf is a village in the German state of Saxony-Anhalt that forms part of the town of Wettin-Löbejün.
-
E.
Dierdorf
Dierdorf is a surname most prominently associated with former American football player and sportscaster Dan Dierdorf.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe387c02108190badf9b5051cd9c7a |
completed | May 8, 2026, 7:24 p.m. |
Created at: April 9, 2026, 10:20 p.m.