Triple
T15072812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switchblade |
E379921
|
entity |
| Predicate | hasMilitaryBackgroundElement |
P38925
|
FINISHED |
| Object | Vietnam War 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: Vietnam War service | Statement: [Switchblade, hasMilitaryBackgroundElement, Vietnam War service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryBackgroundElement Context triple: [Switchblade, hasMilitaryBackgroundElement, Vietnam War service]
-
A.
militaryBackground
chosen
Indicates that an entity has prior or current experience, service, or training in a military organization.
-
B.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
C.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
D.
hasMilitarySpeciality
Indicates that an entity possesses a specific military role, skill set, or area of professional expertise within the armed forces.
-
E.
hadMilitaryPost
Indicates that an entity held an official position or assignment within a military organization.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fa0570819088a97b28173154cd |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.