Triple
T12609497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandro Pertini |
E301073
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pertini |
E301073
|
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: Pertini | Statement: [Sandro Pertini, familyName, Pertini]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pertini Context triple: [Sandro Pertini, familyName, Pertini]
-
A.
Pertini
chosen
Pertini is an Italian surname most famously associated with Sandro Pertini, the former President of Italy and prominent anti-fascist.
-
B.
Parea
Parea is a small coastal village on the island of Huahine in French Polynesia, known for its tranquil beaches and traditional Polynesian atmosphere.
-
C.
Pangallo
Pangallo is an Italian-origin surname borne by individuals such as American politician Dominick Pangallo.
-
D.
Carugo
Carugo is a small municipality in the Province of Como in Lombardy, northern Italy.
-
E.
Formoza
Formoza is an elite Polish naval special operations unit renowned for maritime counter-terrorism, reconnaissance, and high-risk combat missions.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954ea1d748190a848e8a7873e2ea5 |
completed | April 10, 2026, 7:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ecf3e248190868c1eb864191f8b |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:11 p.m.