Triple
T13015190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raimundo |
E322531
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Raimund |
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: Raimund | Statement: [Raimundo, hasVariantForm, Raimund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raimund Context triple: [Raimundo, hasVariantForm, Raimund]
-
A.
Raimund
chosen
Raimund is a masculine given name of Germanic origin, closely related to and often considered a variant of the name Raymond.
-
B.
Aleandro
Aleandro is an Italian surname historically associated with notable Catholic churchmen and papal diplomats.
-
C.
Luciano
Luciano is a masculine given name of Italian origin, famously borne by the renowned operatic tenor Luciano Pavarotti.
-
D.
Emilio
Emilio is a masculine given name of Spanish and Italian origin, borne by various notable figures including military leaders, artists, and politicians.
-
E.
Raimundus
Raimundus is a Latinized given name historically used across medieval Europe, often associated with various saints, scholars, and nobles.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecd04748190ade2530ee5db35fe |
completed | April 10, 2026, 10:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbc98e10819091d71198bca1ac12 |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:50 p.m.