Triple
T38218689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M41A pulse rifle |
E1010750
|
entity |
| Predicate | designedByInUniverseCompany |
P184
|
FINISHED |
| Object | Armat Battlefield Systems |
—
|
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: Armat Battlefield Systems | Statement: [M41A pulse rifle, designedByInUniverseCompany, Armat Battlefield Systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedByInUniverseCompany Context triple: [M41A pulse rifle, designedByInUniverseCompany, Armat Battlefield Systems]
-
A.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
designedByCompanyFoundedBy
Indicates that something was designed by a company that was founded by a specified entity.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
designersInUniverse
Indicates that certain designers exist or are present within a specified universe or conceptual domain.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:30 p.m.