Triple
T4245106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrocław Opera |
E95508
|
entity |
| Predicate | significantBuildingFeature |
P6684
|
FINISHED |
| Object | classical façade |
—
|
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: classical façade | Statement: [Wrocław Opera, significantBuildingFeature, classical façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantBuildingFeature Context triple: [Wrocław Opera, significantBuildingFeature, classical façade]
-
A.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
-
B.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
-
D.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
E.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8c42e88190b309a1ef7f6529ac |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.