Triple
T12348029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raginmund |
E294407
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Raimundr |
E754312
|
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: Raimundr | Statement: [Raginmund, hasVariant, Raimundr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raimundr Context triple: [Raginmund, hasVariant, Raimundr]
-
A.
Raimundus
Raimundus is a Latinized given name historically used across medieval Europe, often associated with various saints, scholars, and nobles.
-
B.
Reimund
Reimund is a masculine given name, primarily used in German-speaking regions, that is a variant of the name Raymond.
-
C.
Raimund
chosen
Raimund is a masculine given name of Germanic origin, closely related to and often considered a variant of the name Raymond.
-
D.
Raymun
Raymun is a town located within Jordan's Jerash (Jarash) Governorate, known for its rural setting in the country's north.
-
E.
Raimond
Raimond is a masculine given name of Germanic origin, commonly considered a variant spelling of Raymond and used in various European countries.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7ba17481908b03af7316b28d9b |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63ef437d08190b09132fa090504a5 |
completed | May 2, 2026, 6:14 p.m. |
Created at: April 8, 2026, 9:53 p.m.