Triple
T17037076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucy |
E413348
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Lucia |
E219616
|
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: Lucia | Statement: [Lucy, hasVariant, Lucia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lucia Context triple: [Lucy, hasVariant, Lucia]
-
A.
Lucia
chosen
Lucia is a feminine given name of Latin origin, commonly associated with light and used in various European cultures.
-
B.
Luciana
Luciana is a feminine given name of Latin origin, commonly used in Spanish- and Portuguese-speaking countries.
-
C.
Valeria
Valeria was a late Roman province in the region of Pannonia, located in what is now western Hungary and parts of neighboring countries.
-
D.
Valeria
Valeria is the honorific epithet associated with the ancient Roman legion Legio XX Valeria Victrix, reflecting its distinguished status and achievements.
-
E.
Valeria
Valeria is a feminine given name used in various languages, derived from the Latin family name Valerius and associated with meanings related to strength and valor.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f38b58819093af4054c3459726 |
completed | April 18, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012338a95c8190951db96209edb61a |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.