Triple
T31657109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar Crest College |
E807884
|
entity |
| Predicate | focusOnCommunityService |
P43777
|
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: [Cedar Crest College, focusOnCommunityService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusOnCommunityService Context triple: [Cedar Crest College, focusOnCommunityService, yes]
-
A.
focusesOnCommunity
chosen
Indicates that the subject prioritizes and directs attention or effort toward the well-being, needs, or development of a community.
-
B.
sharesCommunityServices
Indicates that two or more entities use, provide, or are served by the same community-based services or facilities.
-
C.
communityService
Indicates participation in activities intended to benefit or support a community, typically performed voluntarily or as a civic responsibility.
-
D.
servesCommunityFunction
Indicates that something performs a role or provides a service that benefits or supports a community as a whole.
-
E.
servesCommunityDescribedAs
Indicates that an entity provides services or support to a community characterized or described in a particular way.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 30, 2026, 10:55 p.m.