Triple

T38065211
Position Surface form Disambiguated ID Type / Status
Subject Architecture Library E950451 entity
Predicate catalogAccessibleVia P1985 FINISHED
Object CUHK Library online catalog NE NERFINISHED

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: CUHK Library online catalog | Statement: [Architecture Library, catalogAccessibleVia, CUHK Library online catalog]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: catalogAccessibleVia
Context triple: [Architecture Library, catalogAccessibleVia, CUHK Library online catalog]
  • A. catalogueAccess
    Indicates that an entity has permission to view or interact with a specified catalogue or collection of items.
  • B. accessibleFrom chosen
    Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
  • C. accessibleOn
    Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
  • D. accessibleAs
    Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
  • E. catalogueFor
    Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
  • 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_69f76f01e63c819093b6012fc974f35a completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcc42cbac48190b8d3e4c9ce140838 completed May 7, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69fcb0fc69c88190800453eb57a7e62c completed May 7, 2026, 3:34 p.m.
Created at: May 3, 2026, 4:21 p.m.