Triple

T9332604
Position Surface form Disambiguated ID Type / Status
Subject SOLO (Search Oxford Libraries Online) E224558 entity
Predicate allowsAccessFrom P1985 FINISHED
Object on-campus networks 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-campus networks | Statement: [SOLO (Search Oxford Libraries Online), allowsAccessFrom, on-campus networks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsAccessFrom
Context triple: [SOLO (Search Oxford Libraries Online), allowsAccessFrom, on-campus networks]
  • A. alsoAccessibleFrom
    Indicates that a location, resource, or entity can be reached or obtained not only from one specified source or path but from an additional source or path as well.
  • B. accessIs
    Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
  • C. accessibleFrom chosen
    Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
  • D. accessRestriction
    Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
  • E. controlsAccessBetween
    Indicates that one entity regulates, manages, or restricts the ability of another entity to interact or communicate with a third 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_69ca8427a0c08190b749831d5ea98f02 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd37afceb88190ad7ffbc7b47a1caa completed April 1, 2026, 3:20 p.m.
PD Predicate disambiguation batch_69cc7a643924819097f01144734901cf completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:39 p.m.