Triple
T15369495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weisses Haus in Dangast |
E367504
|
entity |
| Predicate | depictsArchitecture |
P1581
|
FINISHED |
| Object | residential house |
—
|
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: residential house | Statement: [Weisses Haus in Dangast, depictsArchitecture, residential house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsArchitecture Context triple: [Weisses Haus in Dangast, depictsArchitecture, residential house]
-
A.
architecturalIllustrationsBy
Indicates a relationship where one entity has produced or created architectural illustrations for another entity.
-
B.
renderingArchitecture
Indicates the specific rendering system or framework used to generate visual output for a given entity or environment.
-
C.
depicts
chosen
Indicates that one entity visually represents, portrays, or shows another entity.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
architectureProfileOf
Indicates that one entity serves as the architectural specification, style, or structural design profile that characterizes or defines another entity.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4b88a881909f9575c02aed287d |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.