Triple
T17879796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enlisted Personnel Management Directorate |
E447051
|
entity |
| Predicate | handlesProcess |
P1410
|
FINISHED |
| Object | enlisted assignment orders |
—
|
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: enlisted assignment orders | Statement: [Enlisted Personnel Management Directorate, handlesProcess, enlisted assignment orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesProcess Context triple: [Enlisted Personnel Management Directorate, handlesProcess, enlisted assignment orders]
-
A.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
B.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
C.
handlesAgent
Indicates that one entity is responsible for managing, dealing with, or taking care of another entity (the agent).
-
D.
requiresProcessingBy
Indicates that one entity must undergo handling, treatment, or transformation performed by another entity before a condition is met or a process can continue.
-
E.
handlingProperty
Indicates that one entity specifies how another entity should be handled, processed, or treated under certain conditions.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c0d219481909830fc269fc6beb5 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.