Triple
T3941801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europaturm |
E92049
|
entity |
| Predicate | currentPublicAccess |
P1079
|
FINISHED |
| Object | no regular public access |
—
|
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: no regular public access | Statement: [Europaturm, currentPublicAccess, no regular public access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPublicAccess Context triple: [Europaturm, currentPublicAccess, no regular public access]
-
A.
isPubliclyAccessible
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
B.
publicAccess
chosen
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
C.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
-
D.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
E.
openToPublicSince
Indicates that an entity has been accessible or available for use by the general public starting from a specified point in time.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.