Triple
T25434430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NURSE Corps |
E637337
|
entity |
| Predicate | serviceObligationType |
P445
|
FINISHED |
| Object | full-time service |
—
|
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: full-time service | Statement: [NURSE Corps, serviceObligationType, full-time service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceObligationType Context triple: [NURSE Corps, serviceObligationType, full-time service]
-
A.
obligationType
chosen
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
B.
coreObligation
Indicates that one entity has a primary, essential duty or responsibility owed to another entity or with respect to a particular action or state.
-
C.
obligationCondition
Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
-
D.
obligationBasis
Indicates the foundational reason, source, or justification upon which an obligation is based.
-
E.
obligationScope
Indicates that an obligation applies within a specified scope, context, or domain that constrains where or to what the obligation pertains.
- 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_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 1:59 p.m.