Triple
T14817709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrea Sacchi |
E348361
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Sacchi |
E1072145
|
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: Sacchi | Statement: [Andrea Sacchi, familyName, Sacchi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sacchi Context triple: [Andrea Sacchi, familyName, Sacchi]
-
A.
Sacchi
chosen
Sacchi is an Italian surname most famously associated with Arrigo Sacchi, the influential former AC Milan and Italy national team football manager.
-
B.
Mazo
Mazo is a locality situated on the border of the municipality of El Paso in the Canary Island of La Palma, Spain.
-
C.
Santok
Santok is a historic village in western Poland, long known as a strategic fortified settlement at the confluence of the Noteć and Warta rivers.
-
D.
Schatz
Schatz is a German-language surname borne by various individuals of German and Jewish heritage.
-
E.
Tettamanzi
Tettamanzi is an Italian surname most notably associated with Cardinal Dionigi Tettamanzi, a prominent figure in the Roman Catholic Church.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe2c1ec81908b3dff7a5d0e85d0 |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe3897691c819085ef89480e730723 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:50 a.m.