Triple
T16478746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blessagno |
E400258
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Schignano |
E403167
|
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: Schignano | Statement: [Blessagno, sharesBorderWith, Schignano]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schignano Context triple: [Blessagno, sharesBorderWith, Schignano]
-
A.
Schignano
chosen
Schignano is a small Italian village in the Lombardy region, known for its traditional Alpine setting and historic Carnival celebrations.
-
B.
Zagarolo
Zagarolo is a historic hill town in the Lazio region of central Italy, known for its medieval center and proximity to Rome.
-
C.
Contigliano
Contigliano is a small town and comune in the province of Rieti in the Lazio region of central Italy.
-
D.
Poggiardo
Poggiardo is a small town in the Apulia region of southern Italy, known for its archaeological sites and traditional Salento culture.
-
E.
Poggiorsini
Poggiorsini is a small Italian town and comune in the Apulia region of southern Italy.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e01230881908b2147a25f78b7f4 |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00679ecf4c819096e7f698b81fe25a |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:13 a.m.