Triple
T7582934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludo |
E179533
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Ludovica |
E33585
|
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: Ludovica | Statement: [Ludo, relatedName, Ludovica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ludovica Context triple: [Ludo, relatedName, Ludovica]
-
A.
Ludovica
chosen
Ludovica is an Italian feminine given name, traditionally associated with nobility and derived from the same Germanic roots as names like Louise and Ludwig.
-
B.
Vincenza
Vincenza is an Italian feminine given name, commonly used as the female counterpart of Vincenzo.
-
C.
Vittoria
Vittoria is the Italian form of the name Victoria, commonly used as a female given name and place name in Italy.
-
D.
Letizia
Letizia is a feminine given name of Italian origin, famously borne by Maria Letizia Ramolino, the mother of Napoleon Bonaparte.
-
E.
Ludovika
Ludovika is a feminine given name, used as a variant spelling of Ludovica in various European languages.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9794034819088de196c3519a665 |
completed | March 27, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c87080c19c8190ba6a632f6f277621 |
completed | March 29, 2026, 12:21 a.m. |
Created at: March 27, 2026, 3:52 p.m.