Triple
T8046270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadio Mario Rigamonti |
E187560
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Brescia |
E208736
|
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: Brescia | Statement: [Stadio Mario Rigamonti, city, Brescia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brescia Context triple: [Stadio Mario Rigamonti, city, Brescia]
-
A.
Brescia
chosen
Brescia is a historic industrial and cultural city in northern Italy, known for its Roman and medieval architecture and its role as an economic hub.
-
B.
Bergamo
Bergamo is a historic city in northern Italy known for its medieval walled upper town, rich artistic heritage, and strategic location at the foothills of the Alps.
-
C.
Varese
Varese is a city in northern Italy known for its lakeside setting, surrounding Prealps, and role as an important economic and cultural center in the Lombardy region.
-
D.
Trento
Trento is a historic city in northern Italy, known as the capital of Trentino and for its significant role in Catholic history and Alpine culture.
-
E.
Schio
Schio is an industrial town in northeastern Italy known historically for its textile production and location in the Veneto region.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4d9ddc8190a7dcf85ed47ee6c3 |
completed | March 31, 2026, 3:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffd37b54881908c67d5746f9ef39e |
completed | April 3, 2026, 5:47 p.m. |
Created at: March 30, 2026, 5:24 p.m.