Triple
T22183461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hundertwasserhaus |
E548229
|
entity |
| Predicate | publicAccessToInterior |
P1079
|
FINISHED |
| Object | restricted |
—
|
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: restricted | Statement: [Hundertwasserhaus, publicAccessToInterior, restricted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicAccessToInterior Context triple: [Hundertwasserhaus, publicAccessToInterior, restricted]
-
A.
interiorAccess
Indicates that one entity provides a way to enter or move within the inside space of another entity.
-
B.
publicAccess
chosen
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
C.
mainAccessFor
Indicates that one entity serves as the primary means or route of access for another entity.
-
D.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
E.
accessibleWithin
Indicates that one entity can be reached, used, or entered from within the spatial or contextual bounds of 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa687808190b9959d4e91db948a |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.