Triple
T12253862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberursel |
E292046
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Ursem |
E759608
|
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: Ursem | Statement: [Oberursel, hasTwinTown, Ursem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ursem Context triple: [Oberursel, hasTwinTown, Ursem]
-
A.
Ursem
chosen
Ursem is a village in the Dutch province of North Holland, known for its rural character and traditional polder landscape.
-
B.
Naberius
Naberius is the main demonic antagonist in the film "I, Frankenstein," depicted as a powerful prince of demons seeking to harness reanimation technology for his own dark purposes.
-
C.
Ulrych
Ulrych is a variant spelling of the Germanic given name Ulrich, commonly used in Central and Eastern European contexts.
-
D.
Alvarus
Alvarus is a Latinized variant of the given name Alvar, historically used in medieval and ecclesiastical contexts.
-
E.
Flerzheim
Flerzheim is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cc849308190b6ff416f8b4f01e8 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60abdc5988190a19104385f54fb06 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:52 p.m.