Triple
T6433483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmontese Baroque |
E129833
|
entity |
| Predicate | hasNotableCity |
P2813
|
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: [Piedmontese Baroque, hasNotableCity, Rivoli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rivoli Context triple: [Piedmontese Baroque, hasNotableCity, 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.
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.
-
E.
Moncalieri
Moncalieri is a historic town near Turin in the Piedmont region of northern Italy, known for its royal Savoy residence and medieval center.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693de6ac81909f3e330363a52102 |
completed | March 22, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640efd490819084b3b67b3b0680b6 |
completed | March 27, 2026, 8:33 a.m. |
Created at: March 22, 2026, 4:45 p.m.