Triple
T37013569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Trop |
E916013
|
entity |
| Predicate | militaryStatusAtIssue |
P65983
|
FINISHED |
| Object | deserter |
—
|
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: deserter | Statement: [Albert Trop, militaryStatusAtIssue, deserter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryStatusAtIssue Context triple: [Albert Trop, militaryStatusAtIssue, deserter]
-
A.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
-
B.
hasMilitaryStatus
chosen
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
C.
militaryStatusChange
Indicates a change in an entity’s military status, such as entering, leaving, or transitioning between roles or service conditions within the armed forces.
-
D.
enlistmentStatus
Indicates the current state or condition of an entity’s participation in a military or similar service (e.g., enlisted, discharged, pending).
-
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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:14 p.m.