Triple
T6171616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Public Library main branch |
E137712
|
entity |
| Predicate | hasPublicComputers |
P19443
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cambridge Public Library main branch, hasPublicComputers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicComputers Context triple: [Cambridge Public Library main branch, hasPublicComputers, true]
-
A.
hasComputerWorkstations
chosen
Indicates that an entity is equipped with or provides access to computer workstations.
-
B.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
C.
hasPublicAddressSystem
Indicates that an entity is equipped with or includes a public address (PA) system for broadcasting audio announcements.
-
D.
hasSupercomputer
Indicates that an entity possesses, controls, or is equipped with a supercomputer.
-
E.
hasPublicHouse
Indicates that one entity possesses, operates, or is associated with a public house (such as a bar or pub) as part of its facilities or holdings.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d910c3c8190ae6af548259295ff |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.