Triple
T31085945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James J. Archer |
E792234
|
entity |
| Predicate | previousMilitaryService |
P35775
|
FINISHED |
| Object | United States Army |
—
|
NE NERFINISHED |
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: United States Army | Statement: [James J. Archer, previousMilitaryService, United States Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMilitaryService Context triple: [James J. Archer, previousMilitaryService, United States Army]
-
A.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
-
B.
involvesMilitaryService
Indicates that the relationship or situation includes participation in, obligation to, or association with formal military service.
-
C.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
D.
placeOfMilitaryService
chosen
Indicates the location or institution where a person performed their military service.
-
E.
stanceOnMilitaryService
Indicates an entity’s expressed position, attitude, or policy regarding military service.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 9:02 p.m.