Triple
T25434424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NURSE Corps |
E637337
|
entity |
| Predicate | requiresCommitmentTo |
P17418
|
FINISHED |
| Object | service in underserved communities |
—
|
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: service in underserved communities | Statement: [NURSE Corps, requiresCommitmentTo, service in underserved communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCommitmentTo Context triple: [NURSE Corps, requiresCommitmentTo, service in underserved communities]
-
A.
coreCommitment
Indicates a fundamental, central obligation or promise that defines the primary responsibility or dedication within a relationship or agreement.
-
B.
requiresAgreementWith
Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
-
C.
commitment
chosen
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
-
D.
guaranteeCommitments
Indicates a relationship where one party formally assures that specific obligations or promises made to another party will be fulfilled or upheld.
-
E.
requiresProofIn
Indicates that one entity must be justified, validated, or supported by formal proof within the context or framework specified by another entity.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 1:59 p.m.