Triple
T1865740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEPS |
E34915
|
entity |
| Predicate | applicantOutcome |
P22603
|
FINISHED |
| Object | qualification for military service |
—
|
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: qualification for military service | Statement: [MEPS, applicantOutcome, qualification for military service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicantOutcome Context triple: [MEPS, applicantOutcome, qualification for military service]
-
A.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
B.
outcomeType
chosen
Indicates the specific category or nature of the result produced by an event, process, or action.
-
C.
initialOutcome
Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
-
D.
eligibleAppointees
Indicates that certain individuals or entities meet the required criteria to be considered for a particular appointment or position.
-
E.
rejectedAt
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.