Triple
T29114944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heckler & Koch MG5 |
E737018
|
entity |
| Predicate | hasStock |
P194743
|
FINISHED |
| Object | adjustable buttstock |
—
|
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: adjustable buttstock | Statement: [Heckler & Koch MG5, hasStock, adjustable buttstock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStock Context triple: [Heckler & Koch MG5, hasStock, adjustable buttstock]
-
A.
hasStockPosition
Indicates that an entity holds a quantity of a particular stock, typically specifying ownership, size, and possibly direction (long or short) of the investment position.
-
B.
stockedWith
Indicates that one entity is supplied or filled with a particular item or resource by another entity.
-
C.
hasStockCharacter
Indicates that a work of fiction includes a stereotypical or commonly recurring character type as part of its cast.
-
D.
hasStockType
Indicates that an entity possesses or is associated with a particular category or type of stock.
-
E.
hasStockSeries
Indicates that an entity is associated with a particular stock time series or sequence of stock-related data.
- F. None of above. chosen
Provenance (4 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: April 28, 2026, 11:21 a.m.