Triple
T22786081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piazzale Olimpia |
E563969
|
entity |
| Predicate | isInCityFamousFor |
P144057
|
FINISHED |
| Object | historic center of Verona |
—
|
LITERAL 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: historic center of Verona | Statement: [Piazzale Olimpia, isInCityFamousFor, historic center of Verona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCityFamousFor Context triple: [Piazzale Olimpia, isInCityFamousFor, historic center of Verona]
-
A.
isInTownKnownFor
chosen
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
B.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
C.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
D.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
E.
alsoAttractsTouristsIn
Indicates that a place, in addition to another, draws or appeals to tourists within a specified location or context.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c321f848190a4443aa6bb4e57d7 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.