Triple
T37370966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saco Defense |
E927840
|
entity |
| Predicate | suppliedProduct |
P137951
|
FINISHED |
| Object | military small arms for U.S. armed forces |
—
|
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: military small arms for U.S. armed forces | Statement: [Saco Defense, suppliedProduct, military small arms for U.S. armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliedProduct Context triple: [Saco Defense, suppliedProduct, military small arms for U.S. armed forces]
-
A.
providedProduct
chosen
Indicates that one entity has supplied or made available a particular product to another entity.
-
B.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
C.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
D.
suppliedAs
Indicates that one entity is provided, delivered, or made available in the form, role, or capacity of another entity.
-
E.
acquiredProduct
Indicates that one entity has obtained ownership or control of another entity through an acquisition.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.