Triple
T5987477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montebelluna |
E133263
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Treviso |
E160032
|
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: Treviso | Statement: [Montebelluna, locatedNear, Treviso]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Treviso Context triple: [Montebelluna, locatedNear, Treviso]
-
A.
Treviso
chosen
Treviso is a historic city in northeastern Italy’s Veneto region, known for its medieval walls, canals, and proximity to Venice.
-
B.
Padua
Padua is a historic city in northern Italy renowned as a major cultural and academic center, home to one of Europe’s oldest universities.
-
C.
Vicenza
Vicenza is a historic city in northeastern Italy renowned for its Palladian architecture and cultural heritage.
-
D.
Rovigo
Rovigo is a small historic city in northeastern Italy known for its medieval architecture and location in the fertile Po River plain.
-
E.
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.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc38a308190a368c5c787a5fc64 |
completed | March 22, 2026, 8:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c518b75da08190829e7e746f99f5ac |
completed | March 26, 2026, 11:29 a.m. |
Created at: March 22, 2026, 4:04 p.m.