Triple
T26698030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Nurse Corps |
E673077
|
entity |
| Predicate | deployedDuty |
P58267
|
FINISHED |
| Object | forward surgical teams |
—
|
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: forward surgical teams | Statement: [Army Nurse Corps, deployedDuty, forward surgical teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deployedDuty Context triple: [Army Nurse Corps, deployedDuty, forward surgical teams]
-
A.
hasDutyStatus
Indicates that an entity currently holds a particular duty or operational status in relation to a role, task, or assignment.
-
B.
performsDuty
chosen
Indicates that one entity carries out or fulfills a responsibility, task, or obligation on behalf of or in relation to another entity.
-
C.
createsDuty
Indicates that one entity brings about an obligation or responsibility for another entity to perform or uphold something.
-
D.
dutyTime
Indicates the period during which an entity is officially on duty or expected to perform assigned responsibilities.
-
E.
garrisonDuty
Indicates a relationship where an entity is assigned to stay and defend or guard a specific location as part of its military or protective duties.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:29 a.m.