Triple
T7004889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonso |
E162427
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Alfonzo |
E207978
|
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: Alfonzo | Statement: [Alfonso, hasVariant, Alfonzo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alfonzo Context triple: [Alfonso, hasVariant, Alfonzo]
-
A.
Alonzo
chosen
Alonzo is a given name most notably borne by the American mathematician and logician Alonzo Church, a founder of theoretical computer science and lambda calculus.
-
B.
Ambrosio
Ambrosio is the devout yet ultimately corrupt and tragic monastic protagonist of Matthew Gregory Lewis’s Gothic novel "The Monk."
-
C.
Aleandro
Aleandro is an Italian surname historically associated with notable Catholic churchmen and papal diplomats.
-
D.
Armando
Armando is a masculine given name of Spanish and Portuguese origin, commonly used in many Spanish-speaking countries.
-
E.
Alfrédo
Alfrédo is a given name, likely a variant or cognate of "Alfred" or "Alfredo," used as a personal male first name in various 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc14037c81908bb87250ef29be50 |
completed | March 27, 2026, 7:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7755c7c1481908eed49c72726195e |
completed | March 28, 2026, 6:29 a.m. |
Created at: March 27, 2026, 2:33 p.m.