Triple
T36726769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palazzo Garampi |
E907215
|
entity |
| Predicate | locatedInHistoricSquare |
P117795
|
FINISHED |
| Object | Piazza Cavour |
E557238
|
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: Piazza Cavour | Statement: [Palazzo Garampi, locatedInHistoricSquare, Piazza Cavour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHistoricSquare Context triple: [Palazzo Garampi, locatedInHistoricSquare, Piazza Cavour]
-
A.
isLocatedInHistoricSquare
chosen
Indicates that an entity is situated within a square that is recognized as historically significant.
-
B.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
-
C.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
D.
hasHistoricTownSquare
Indicates that an entity possesses or includes a town square that is of historical significance.
-
E.
locatedInTimeSquareArea
Indicates that the entity is situated within the geographic area commonly defined as Times Square.
- F. None of above.
Provenance (4 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c19b0588190ba99774618d6223e |
completed | June 26, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.