Triple
T5882486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anpezan |
E130780
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Ampezzan Ladin |
E151728
|
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: Ampezzan Ladin | Statement: [Anpezan, closelyRelatedTo, Ampezzan Ladin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ampezzan Ladin Context triple: [Anpezan, closelyRelatedTo, Ampezzan Ladin]
-
A.
Lomazzo
Lomazzo is a town in northern Italy’s Lombardy region, situated between Como and Milan and known for its residential character and local industry.
-
B.
Arzerello
Arzerello is a locality or frazione within the municipality of Piove di Sacco in the Veneto region of northern Italy.
-
C.
Ornavasso
Ornavasso is a town in northern Italy notable for its rich archaeological remains linked to the ancient Lepontic Celtic culture.
-
D.
Ampezzo
chosen
Ampezzo is a town in the Dolomite region of northern Italy known for its Ladin cultural and linguistic heritage.
-
E.
Brunico
Brunico is a historic town and popular tourist center in northern Italy’s Alps, known for its medieval old town, castle, and proximity to the Dolomites.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03673ecd88190978993056b675259 |
completed | March 22, 2026, 6:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0bff29200819080c7d9269ad80c53 |
completed | March 23, 2026, 4:22 a.m. |
Created at: March 22, 2026, 3:57 p.m.