Triple
T14389743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parma Baptistery |
E356809
|
entity |
| Predicate | municipality |
P852
|
FINISHED |
| Object | Comune di Parma |
E426327
|
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: Comune di Parma | Statement: [Parma Baptistery, municipality, Comune di Parma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Comune di Parma Context triple: [Parma Baptistery, municipality, Comune di Parma]
-
A.
Comune di Parma
chosen
Comune di Parma is the municipal government and administrative body responsible for managing the city of Parma in northern Italy.
-
B.
Comune di Prato
Comune di Prato is the municipal government authority responsible for administering the city of Prato in Tuscany, Italy.
-
C.
Comune di Pisa
Comune di Pisa is the municipal government authority of the historic Italian city of Pisa in Tuscany.
-
D.
Comune di Modena
Comune di Modena is the modern Italian municipality that encompasses the historic city of Modena in the Emilia-Romagna region, known for its rich cultural heritage, cuisine, and automotive industry.
-
E.
Comune di Pesaro
Comune di Pesaro is the municipal government authority responsible for administering the city of Pesaro in Italy.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9029ef048190bdda5ee41618e720 |
completed | April 14, 2026, 7:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd551623608190ba1de09b423cc5e1 |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 10, 2026, 1:16 a.m.