Triple
T14683162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGM-179 JAGM |
E344837
|
entity |
| Predicate | intendedServiceBranch |
P15908
|
FINISHED |
| Object | joint 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: joint service | Statement: [AGM-179 JAGM, intendedServiceBranch, joint service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedServiceBranch Context triple: [AGM-179 JAGM, intendedServiceBranch, joint service]
-
A.
branchOfServiceModelledOn
Indicates that one branch of service is modeled, structured, or designed based on another branch of service.
-
B.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
C.
serviceBranchSpecific
Indicates that something is restricted or tailored to a particular branch of service rather than being common across all branches.
-
D.
originalServiceBranch
Indicates the military or organizational service branch in which an individual initially served or was first enlisted.
-
E.
branchOfServiceFocus
chosen
Indicates that one entity is the primary military or organizational branch of service emphasized, specialized in, or targeted by another entity or activity.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.