Triple
T29236866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Archives of Zimbabwe |
E741216
|
entity |
| Predicate | hasPublicAccessPolicy |
P104554
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Archives of Zimbabwe, hasPublicAccessPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicAccessPolicy Context triple: [National Archives of Zimbabwe, hasPublicAccessPolicy, yes]
-
A.
hasUserAccessPolicy
Indicates that a specific access control policy is defined or associated for a user’s permissions or usage of a resource.
-
B.
hasPublicAccessRestrictions
Indicates that there are specific limitations or conditions governing public access to the associated resource or entity.
-
C.
hasPublicSpacePolicy
chosen
Indicates that an entity has an established policy governing the use, management, or regulation of public spaces.
-
D.
isPubliclyAccessible
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
E.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 12:29 p.m.