Triple
T9442001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet des Dessins |
E227666
|
entity |
| Predicate | typicalAccessPolicy |
P9584
|
FINISHED |
| Object | viewing by appointment |
—
|
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: viewing by appointment | Statement: [Cabinet des Dessins, typicalAccessPolicy, viewing by appointment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAccessPolicy Context triple: [Cabinet des Dessins, typicalAccessPolicy, viewing by appointment]
-
A.
typicalPolicyPreference
Indicates that one entity’s policy preference is characteristic or representative of what is usually favored by another entity or group.
-
B.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
C.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
eraPolicy
Indicates that a specific policy was in effect during a particular historical or temporal era.
-
E.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f300cc88190a793712706295c53 |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.