Triple
T31904003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peninsula Library System |
E814498
|
entity |
| Predicate | sharesResourcesAmong |
P30619
|
FINISHED |
| Object | member public libraries |
—
|
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: member public libraries | Statement: [Peninsula Library System, sharesResourcesAmong, member public libraries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesResourcesAmong Context triple: [Peninsula Library System, sharesResourcesAmong, member public libraries]
-
A.
sharesResourcesWith
chosen
Indicates that two entities mutually use, access, or allocate the same resources.
-
B.
sharesResourceType
Indicates that two or more entities use or are associated with the same type or category of resource.
-
C.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
D.
sharesComponentsWith
Indicates that two entities have one or more structural or functional components in common.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, midnight