Triple
T5483279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asinelli Tower |
E123516
|
entity |
| Predicate | hasCitySymbolRole |
P10919
|
FINISHED |
| Object | iconic skyline feature of Bologna |
—
|
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: iconic skyline feature of Bologna | Statement: [Asinelli Tower, hasCitySymbolRole, iconic skyline feature of Bologna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCitySymbolRole Context triple: [Asinelli Tower, hasCitySymbolRole, iconic skyline feature of Bologna]
-
A.
citySymbol
chosen
Indicates that one entity serves as the official symbol or emblem representing a particular city.
-
B.
citySymbolOf
Indicates that a particular city serves as an official symbol or emblem representing another entity, such as a region, organization, or concept.
-
C.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
D.
cantonSymbol
Indicates that one entity serves as the official symbol or emblem representing a particular canton.
-
E.
hasMajorCityRole
Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.