Triple
T7606473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Commendation Medal |
E180116
|
entity |
| Predicate | rankEligibility |
P16384
|
FINISHED |
| Object | enlisted personnel |
—
|
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 personnel | Statement: [Army Commendation Medal, rankEligibility, enlisted personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankEligibility Context triple: [Army Commendation Medal, rankEligibility, enlisted personnel]
-
A.
eligibleRank
chosen
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
B.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
C.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
-
D.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
E.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9fe10408190b1c12bb8f911cea8 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.