Triple
T31906589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcutt, California |
E814568
|
entity |
| Predicate | hasLibraryServiceProvider |
P13887
|
FINISHED |
| Object | Santa Maria Public Library system |
—
|
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: Santa Maria Public Library system | Statement: [Orcutt, California, hasLibraryServiceProvider, Santa Maria Public Library system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLibraryServiceProvider Context triple: [Orcutt, California, hasLibraryServiceProvider, Santa Maria Public Library system]
-
A.
hasServiceProvider
chosen
Indicates that an entity is associated with or supported by a specific service provider.
-
B.
hasLibraries
Indicates that an entity possesses, contains, or is associated with one or more libraries.
-
C.
hasOfficialLibrary
Indicates that an entity possesses or is served by a formally recognized, authorized library.
-
D.
hasPublicLibraryType
Indicates that an entity is associated with a specific type or category of public library.
-
E.
hasServiceModule
Indicates that an entity is equipped with, or associated with, a specific service module that provides supporting or auxiliary functions.
- 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_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, midnight