Triple
T8443628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitchburg Public Library |
E199610
|
entity |
| Predicate | hasComputerAccess |
P19443
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fitchburg Public Library, hasComputerAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComputerAccess Context triple: [Fitchburg Public Library, hasComputerAccess, yes]
-
A.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
B.
hasComputerWorkstations
chosen
Indicates that an entity is equipped with or provides access to computer workstations.
-
C.
hasSupercomputer
Indicates that an entity possesses, controls, or is equipped with a supercomputer.
-
D.
hasOnboardComputer
Indicates that one entity is equipped with or contains an onboard computer system.
-
E.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3122cfc8190ac6103fa4e4a7c45 |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.