Triple
T8784182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remembering |
E209003
|
entity |
| Predicate | appliedToPart |
P84084
|
FINISHED |
| Object | facade of Haus der Kunst |
—
|
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: facade of Haus der Kunst | Statement: [Remembering, appliedToPart, facade of Haus der Kunst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToPart Context triple: [Remembering, appliedToPart, facade of Haus der Kunst]
-
A.
appliesToComponent
chosen
Indicates that a rule, condition, or operation is specifically relevant or applicable to a particular component.
-
B.
appliedToMaterial
Indicates that an action, process, or treatment is performed on or directed toward a specific material.
-
C.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f7441e8819081ea0ae7bc2afde7 |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.