Triple
T2426562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonard |
E53541
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Leonardus |
E53541
|
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: Leonardus | Statement: [Leonard, hasVariant, Leonardus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leonardus Context triple: [Leonard, hasVariant, Leonardus]
-
A.
Laurentius
Laurentius is a Latin given name historically borne by several early Christian saints and later adapted into various European forms such as Laurence and Lawrence.
-
B.
Albertus
Albertus is a masculine given name of Latin origin, commonly used in Dutch and German-speaking regions.
-
C.
Leonhard
Leonhard is a masculine given name most famously borne by the prolific 18th-century Swiss mathematician and physicist Leonhard Euler.
-
D.
Leonard
chosen
Leonard is a masculine given name of Germanic origin, commonly used in English-speaking countries and borne by numerous notable figures in arts, sports, and public life.
-
E.
Johanus
Johanus is a given name, likely a variant or diminutive of Johan, used as a personal first name in some cultures.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc99b95548190b77d36de9adfe3bb |
completed | March 7, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aebf637be4819096874a24e87f84ab |
completed | March 9, 2026, 12:38 p.m. |
Created at: March 6, 2026, 9:42 p.m.