Triple
T23346019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic center of Catania |
E591866
|
entity |
| Predicate | urbanLandscapeCharacterizedBy |
P151962
|
FINISHED |
| Object | lava-stone facades |
—
|
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: lava-stone facades | Statement: [historic center of Catania, urbanLandscapeCharacterizedBy, lava-stone facades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanLandscapeCharacterizedBy Context triple: [historic center of Catania, urbanLandscapeCharacterizedBy, lava-stone facades]
-
A.
cityScene
Indicates a scene or setting that takes place within an urban or city environment.
-
B.
urbanScale
Indicates the extent or magnitude of development, density, or size at which an area or environment can be characterized as urban.
-
C.
urbanLayout
Indicates how the spatial arrangement, organization, and structure of buildings, streets, and public spaces relate to one another within an urban area.
-
D.
withinUrbanArea
Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
-
E.
citySide
Indicates that one entity is located on or along a particular side or edge of a city relative to another reference point.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983697408190b31817174ed4e77b |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:19 p.m.