Triple
T22514834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont railway network |
E556613
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Saluzzo |
—
|
NE NERFINISHED |
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: Saluzzo | Statement: [Piedmont railway network, connectsCity, Saluzzo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saluzzo Context triple: [Piedmont railway network, connectsCity, Saluzzo]
-
A.
Saluzzo
chosen
Saluzzo is a historic town in the Piedmont region of northwestern Italy, known for its well-preserved medieval center and cultural heritage.
-
B.
Ornavasso
Ornavasso is a town in northern Italy notable for its rich archaeological remains linked to the ancient Lepontic Celtic culture.
-
C.
Calolziocorte
Calolziocorte is a town and municipality in the Lombardy region of northern Italy, situated near Lake Como and the Adda River.
-
D.
Grugliasco
Grugliasco is a municipality in the Metropolitan City of Turin in the Piedmont region of northwestern Italy.
-
E.
Zasole
Zasole is a village in southern Poland located near the town of Brzeszcze in the Lesser Poland region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2c3098819098a553133cc9515b |
completed | April 29, 2026, 1:26 a.m. |
Created at: April 16, 2026, 8:50 p.m.