Triple
T7952002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Medical Service Corps |
E184635
|
entity |
| Predicate | officerType |
P60021
|
FINISHED |
| Object | commissioned officers |
—
|
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: commissioned officers | Statement: [Army Medical Service Corps, officerType, commissioned officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officerType Context triple: [Army Medical Service Corps, officerType, commissioned officers]
-
A.
officerCategory
chosen
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
B.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
-
C.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
D.
targetOffenderType
Indicates the specific category or type of offender that an action, rule, or condition is directed toward.
-
E.
isOfficerOf
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5c95908190b6ee900d2b324574 |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:10 p.m.