Triple
T11518853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Street |
E273102
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Rivoli |
E132226
|
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: Rivoli | Statement: [Queen Street, hasLandmark, Rivoli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rivoli Context triple: [Queen Street, hasLandmark, Rivoli]
-
A.
Rivoli
chosen
Rivoli is a town in the Piedmont region of northern Italy, near Turin, known for its historic castle and strategic location.
-
B.
Piossasco
Piossasco is a municipality in the Metropolitan City of Turin in the Piedmont region of northwestern Italy.
-
C.
Bresso
Bresso is a municipality in the Metropolitan City of Milan in northern Italy, known for its dense urban setting and proximity to Milan.
-
D.
Marsella
Marsella is a small Colombian town known for its traditional architecture and coffee-growing culture in the Andean region.
-
E.
Chieri
Chieri is a historic town and comune in the Piedmont region of northwestern Italy, known for its medieval architecture and proximity to the city of Turin.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fcf927081908ef89eff7ad833b0 |
completed | April 10, 2026, 4:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e62540ff4c81909206db0344842c3b |
completed | April 20, 2026, 1:08 p.m. |
Created at: April 8, 2026, 9:36 p.m.