Triple
T10736945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Paul Public Library |
E253217
|
entity |
| Predicate | cardRequiredFor |
P95723
|
FINISHED |
| Object | borrowing materials |
—
|
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: borrowing materials | Statement: [Saint Paul Public Library, cardRequiredFor, borrowing materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardRequiredFor Context triple: [Saint Paul Public Library, cardRequiredFor, borrowing materials]
-
A.
creditRequired
Indicates that a certain amount or type of credit must be obtained or possessed as a prerequisite for something (such as access, participation, or completion).
-
B.
creditCheckRequired
Indicates that a verification of an entity’s creditworthiness must be performed before proceeding with a related action or transaction.
-
C.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
D.
requiresCreditAs
Indicates that one entity must be credited or acknowledged in a specified manner or role in relation to another entity.
-
E.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71022aee0819091a5790d3dee6777 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:14 p.m.