Triple
T27573820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ArmaLite |
E696103
|
entity |
| Predicate | soldDesignRightsOf |
P101340
|
FINISHED |
| Object | AR-15 |
—
|
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: AR-15 | Statement: [ArmaLite, soldDesignRightsOf, AR-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldDesignRightsOf Context triple: [ArmaLite, soldDesignRightsOf, AR-15]
-
A.
soldRightsTo
chosen
Indicates that one party has transferred ownership or usage rights of something to another party, typically in exchange for compensation.
-
B.
designedToSell
Indicates that something was intentionally created or configured for the purpose of being sold.
-
C.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
D.
currentOwnerOfDesign
Indicates that one entity is the present legal or recognized owner of a particular design created or defined by another entity.
-
E.
soldWorkTo
Indicates that one entity transferred ownership of a work (such as a product, artwork, or creation) to another entity in exchange for payment.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:44 p.m.