Triple
T38006301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piazza IX Aprile |
E948242
|
entity |
| Predicate | hasNearbyBuildingStyle |
P52857
|
FINISHED |
| Object | medieval elements |
—
|
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: medieval elements | Statement: [Piazza IX Aprile, hasNearbyBuildingStyle, medieval elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBuildingStyle Context triple: [Piazza IX Aprile, hasNearbyBuildingStyle, medieval elements]
-
A.
hasBuildingStyleInSurroundings
chosen
Indicates that an entity is surrounded by or located in an area characterized by a particular building style.
-
B.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
C.
architecturalStyleSimilarTo
Indicates that two entities share a comparable or closely related architectural style in form, design, or aesthetic characteristics.
-
D.
hasMainBuildingNear
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
-
E.
hasNearbyPropertyType
Indicates that one entity has another entity of a specified property type located in close physical proximity to it.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00b3d2e0c88190a8bf49576e654f64 |
completed | May 10, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_6a00b376f4e48190a6676779fe02ea9f |
completed | May 10, 2026, 4:33 p.m. |
Created at: May 3, 2026, 4:20 p.m.