Triple
T6519275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian libraries |
E148339
|
entity |
| Predicate | userAccess |
P55417
|
FINISHED |
| Object | generally free of charge |
—
|
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: generally free of charge | Statement: [Norwegian libraries, userAccess, generally free of charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userAccess Context triple: [Norwegian libraries, userAccess, generally free of charge]
-
A.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
B.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
C.
hasHumanAccess
chosen
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
D.
accessProvides
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
E.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac11d0e481908103c4b51de9521e |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.