Triple
T10159152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guglielmo |
E233843
|
entity |
| Predicate | hasDiminutive |
P456
|
FINISHED |
| Object | Guglielmino |
E239819
|
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: Guglielmino | Statement: [Guglielmo, hasDiminutive, Guglielmino]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guglielmino Context triple: [Guglielmo, hasDiminutive, Guglielmino]
-
A.
Guglielmino
chosen
Guglielmino is an Italian given name, typically considered a diminutive or variant of Guglielmo (the Italian form of William).
-
B.
Giulianino
Giulianino is an Italian diminutive given name, typically used as an affectionate or smaller form of Giuliano.
-
C.
Manfredi
Manfredi is an architect best known as one of the co-founders and principals of the New York–based architecture firm Weiss/Manfredi.
-
D.
Giannino
Giannino is an Italian given name, commonly used as a familiar or affectionate form of Giovanni.
-
E.
Ignazio
Ignazio is an Italian given name, cognate to Ignacy and typically associated with the Latin-rooted names Ignatius and Ignacio.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3176ac9388190bc76b3cffce93a3d |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:09 p.m.