Triple
T11345075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Soprano |
E268692
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Corrado |
E804778
|
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: Corrado | Statement: [Junior Soprano, givenName, Corrado]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Corrado Context triple: [Junior Soprano, givenName, Corrado]
-
A.
Corrado
chosen
Corrado is an Italian given name, equivalent to the Germanic name Conrad, historically borne by nobles, clergy, and notable figures in Italy.
-
B.
Gaetano
Gaetano is an Italian given name, historically notable as the birth name of Saint Cajetan, a prominent 16th-century Catholic priest and reformer.
-
C.
Fabrizio
Fabrizio is an Italian masculine given name of Latin origin, commonly used in Italy and among Italian-speaking communities.
-
D.
Giulianino
Giulianino is an Italian diminutive given name, typically used as an affectionate or smaller form of Giuliano.
-
E.
Ariberto
Ariberto is an Italian given name, historically borne by medieval nobles and church figures, and used as a variant of the name Aribert.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea1f9574819089760c5b5908f09e |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e55649a9188190911608fef5894bd8 |
completed | April 19, 2026, 10:25 p.m. |
Created at: April 8, 2026, 9:33 p.m.