Triple
T12608762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UJ Library |
E301054
|
entity |
| Predicate | supportsAccessMode |
P6865
|
FINISHED |
| Object | on-site 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: on-site access | Statement: [UJ Library, supportsAccessMode, on-site access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccessMode Context triple: [UJ Library, supportsAccessMode, on-site access]
-
A.
hasAccessMode
chosen
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
B.
supportsAccessModel
Indicates that one entity enables, permits, or is compatible with a particular access model used by another entity.
-
C.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
-
D.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
E.
supportsPermissionType
Indicates that one entity is capable of handling, allowing, or being configured with a specified type of permission.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:11 p.m.