Triple
T13656451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotuit Library |
E326871
|
entity |
| Predicate | servesCommunityRole |
P15115
|
FINISHED |
| Object | cultural center |
—
|
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: cultural center | Statement: [Cotuit Library, servesCommunityRole, cultural center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCommunityRole Context triple: [Cotuit Library, servesCommunityRole, cultural center]
-
A.
roleInCommunity
chosen
Indicates the function, position, or set of responsibilities an entity holds within a particular community or group.
-
B.
servesCommunitiesAlong
Indicates that something provides services or support to the communities located along a particular route, corridor, or area.
-
C.
hasCommunityService
Indicates that an entity is associated with, participates in, or is subject to community service activities or obligations.
-
D.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
hasCommunityServed
Indicates that an entity provides services or benefits to, or is intended to support, a particular community or group of people.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61d56e4819084ae3c16ecdf4a05 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.