Triple
T5543502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Embassy in Berlin |
E145349
|
entity |
| Predicate | occupiesBuildingStyle |
P607
|
FINISHED |
| Object | Stalinist architecture |
—
|
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: Stalinist architecture | Statement: [Russian Embassy in Berlin, occupiesBuildingStyle, Stalinist architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupiesBuildingStyle Context triple: [Russian Embassy in Berlin, occupiesBuildingStyle, Stalinist architecture]
-
A.
hasBuildingStyleInSurroundings
Indicates that an entity is surrounded by or located in an area characterized by a particular building style.
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
buildingStyleOfChamber
Indicates the architectural style or design type associated with a particular chamber.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc947bc81908d1f7b709392ec20 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.