Triple
T4079612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Medical Badge |
E87444
|
entity |
| Predicate | serviceComponentEligibility |
P18203
|
FINISHED |
| Object | Regular Army |
—
|
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: Regular Army | Statement: [Combat Medical Badge, serviceComponentEligibility, Regular Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceComponentEligibility Context triple: [Combat Medical Badge, serviceComponentEligibility, Regular Army]
-
A.
eligibilityContext
Indicates the situational or conditional factors under which an entity qualifies for or is considered eligible for something.
-
B.
eligibilityUnit
chosen
Indicates that one entity serves as the unit or basis used to determine another entity’s eligibility for a benefit, status, or condition.
-
C.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
D.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
E.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5087b081909d6042bfe8d8a306 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.