Triple
T18759500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust Memorial (Nameless Library, Vienna) |
E458731
|
entity |
| Predicate | doorDetail |
P30972
|
FINISHED |
| Object | closed double doors without handles |
—
|
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: closed double doors without handles | Statement: [Holocaust Memorial (Nameless Library, Vienna), doorDetail, closed double doors without handles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorDetail Context triple: [Holocaust Memorial (Nameless Library, Vienna), doorDetail, closed double doors without handles]
-
A.
doorAndWindowDetail
chosen
Indicates a relationship that specifies detailed characteristics or features shared by both doors and windows.
-
B.
doorType
Indicates the specific kind or category of door associated with an entity.
-
C.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
D.
doorLevel
Indicates the security or access level required to open or pass through a particular door.
-
E.
doorSymbol
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d7db2f48190a4f1c5c9801fe180 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.