Triple
T10821052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missoula Public Library |
E255369
|
entity |
| Predicate | hasLibrarySystemRole |
P83028
|
FINISHED |
| Object | main branch |
—
|
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: main branch | Statement: [Missoula Public Library, hasLibrarySystemRole, main branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLibrarySystemRole Context triple: [Missoula Public Library, hasLibrarySystemRole, main branch]
-
A.
hasBorrowingSystem
Indicates that an entity possesses or employs a system or mechanism for borrowing items, resources, or services.
-
B.
hasLibraryBranch
Indicates that an entity possesses or is associated with one or more library branches as part of its organizational structure or services.
-
C.
roleInLibrary
Indicates the specific function, position, or responsibility an entity holds within a library context.
-
D.
hasLibraryHoldings
Indicates that a library possesses or maintains specific items or collections within its holdings.
-
E.
libraryRole
chosen
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73449eee88190afa52c4e6ef96baa |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.