Triple
T29324391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicepresidente del Consiglio dei ministri |
E743602
|
entity |
| Predicate | sedeIstituzionale |
P135051
|
FINISHED |
| Object | Palazzo Chigi |
—
|
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: Palazzo Chigi | Statement: [Vicepresidente del Consiglio dei ministri, sedeIstituzionale, Palazzo Chigi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sedeIstituzionale Context triple: [Vicepresidente del Consiglio dei ministri, sedeIstituzionale, Palazzo Chigi]
-
A.
seatOfGovernment
Indicates that a location serves as the administrative center where a government exercises its official authority and conducts its primary governing functions.
-
B.
headquartersOfOffice
chosen
Indicates that a particular location serves as the main headquarters for a specified office or organizational unit.
-
C.
locationOfGoverningBody
Indicates the place where a governing body is based or carries out its official functions.
-
D.
placeOfOffice
Indicates the location where an office or official position is held or based.
-
E.
administrativeHeadquarter
Indicates the location that serves as the main administrative center or headquarters for an organization or governing body.
- F. None of above.
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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66894ce4c8190b1104ea889b98a8e |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:25 p.m.