Triple
T18395568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall of Zrenjanin |
E449857
|
entity |
| Predicate | hasFacadeElement |
P31480
|
FINISHED |
| Object | ornamental stucco |
—
|
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: ornamental stucco | Statement: [City Hall of Zrenjanin, hasFacadeElement, ornamental stucco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacadeElement Context triple: [City Hall of Zrenjanin, hasFacadeElement, ornamental stucco]
-
A.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
-
B.
hasFacadeOrganization
Indicates that one organization functions as a façade or front for another organization, concealing the latter’s true role or identity.
-
C.
hasFacet
Indicates that an entity possesses a particular aspect, side, or dimension as one of its distinguishable parts or characteristics.
-
D.
facadeFeature
chosen
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
E.
hasDigitalFacade
Indicates that an entity possesses a digital interface or representation that serves as its outward-facing surface or presentation.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51846bb4c8190990f42a792a78ee0 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.