Triple
T14913653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Sergeant Major of the Army Reserve |
E371326
|
entity |
| Predicate | isEnlisted |
P109150
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Command Sergeant Major of the Army Reserve, isEnlisted, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEnlisted Context triple: [Command Sergeant Major of the Army Reserve, isEnlisted, true]
-
A.
hasEnlistedRank
chosen
Indicates that an individual holds an enlisted (non-officer) rank within a military or similar hierarchical organization.
-
B.
enrolledIn
Indicates that one entity is formally registered as a participant in a course, program, or institution represented by another entity.
-
C.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
D.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
E.
eligibleIn
Indicates that an entity meets the necessary conditions or criteria to qualify for participation, use, or consideration within a specified context, domain, or scope.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61f1d488190995f847f84d72cdc |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:27 a.m.