Triple
T26540321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estival Jazz |
E671368
|
entity |
| Predicate | citySquareUsed |
P160618
|
FINISHED |
| Object | Piazza della Riforma |
—
|
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: Piazza della Riforma | Statement: [Estival Jazz, citySquareUsed, Piazza della Riforma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citySquareUsed Context triple: [Estival Jazz, citySquareUsed, Piazza della Riforma]
-
A.
citySquareConnected
Indicates that two locations are directly linked or accessible to each other via a city square.
-
B.
hasCityBlockUse
Indicates that a particular city block is assigned or associated with a specific type of land use or functional purpose.
-
C.
squareUse
Indicates that one entity uses or occupies another entity in a square or rectangular configuration, typically implying a grid-like or evenly spaced arrangement.
-
D.
usedInCity
Indicates that something is utilized, applied, or operates within the context or boundaries of a particular city.
-
E.
hasPublicSquareInFront
Indicates that a building or structure has a public square located directly in front of it.
- F. None of above. chosen
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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6143085b48190940d653f05f96487 |
completed | May 2, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:41 a.m.