Triple

T27029344
Position Surface form Disambiguated ID Type / Status
Subject Toronto Public Library E680875 entity
Predicate hasLibraryCardRequirement P179909 FINISHED
Object free for Toronto residents 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: free for Toronto residents | Statement: [Toronto Public Library, hasLibraryCardRequirement, free for Toronto residents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLibraryCardRequirement
Context triple: [Toronto Public Library, hasLibraryCardRequirement, free for Toronto residents]
  • A. libraryAccess
    Indicates that one entity is permitted to enter, use, or otherwise utilize the resources or services of a library controlled or provided by another entity.
  • B. hasTicketRequirement
    Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
  • C. isLendingLibrary
    Indicates that an entity functions as a library that lends items (such as books or media) to users.
  • D. isNonLendingLibrary
    Indicates that the library does not lend out its materials to patrons.
  • E. servedByLibrary
    Indicates that an entity receives services, resources, or support from a particular library.
  • F. None of above. chosen

Provenance (4 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_69eeeb5566f08190813daf896fa3da04 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
PDg Predicate description generation batch_69f72920c6208190aa4aba6cb6193109 completed May 3, 2026, 10:53 a.m.
Created at: April 27, 2026, 7:13 a.m.