Triple
T8032645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perledo |
E187023
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Bellano |
E755609
|
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: Bellano | Statement: [Perledo, borders, Bellano]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bellano Context triple: [Perledo, borders, Bellano]
-
A.
Bellano
chosen
Bellano is a picturesque town on the eastern shore of Lake Como in northern Italy, known for its lakeside promenade and the dramatic Orrido di Bellano gorge.
-
B.
Melegnano
Melegnano is a town in the Lombardy region of northern Italy, historically notable as the site of major Renaissance-era battles including the Battle of Marignano.
-
C.
Gaggiano
Gaggiano is a small municipality in the Lombardy region of northern Italy, located near Milan and known for its historic canals and rural surroundings.
-
D.
Lissone
Lissone is a town in the Lombardy region of northern Italy, known as part of the Brianza area and recognized for its furniture and design industry.
-
E.
Segrate
Segrate is a municipality in the Metropolitan City of Milan in northern Italy, known for its proximity to Milan and its role as a residential and commercial suburb.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ef18da48190835454a5eb969da7 |
completed | March 31, 2026, 3:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6e5358888190ad1b5771ca00a097 |
completed | April 3, 2026, 7:37 a.m. |
Created at: March 30, 2026, 5:22 p.m.