Triple
T6122038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piave River |
E136506
|
entity |
| Predicate | emptiesNear |
P408
|
FINISHED |
| Object | Cortellazzo |
E389393
|
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: Cortellazzo | Statement: [Piave River, emptiesNear, Cortellazzo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cortellazzo Context triple: [Piave River, emptiesNear, Cortellazzo]
-
A.
Cortellazzo
chosen
Cortellazzo is an Italian locality whose name is associated with the noble title "Countess of Cortellazzo and Buccari."
-
B.
Lizzano
Lizzano is a town and comune in the Apulia region of southern Italy, known for its wine production and proximity to the Ionian coast.
-
C.
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.
-
D.
Fassano
Fassano is an alternative name for the village of Fodom in the Veneto region of northern Italy.
-
E.
Varedo
Varedo is a municipality in the Lombardy region of northern Italy, located in the province of Monza and Brianza.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bf16ad48190958cc46510e02bd3 |
completed | March 22, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c135a5c428819090066ad785296736 |
completed | March 23, 2026, 12:44 p.m. |
Created at: March 22, 2026, 4:14 p.m.