Triple
T27573821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ArmaLite |
E696103
|
entity |
| Predicate | soldDesignRightsTo |
P101340
|
FINISHED |
| Object | Colt's Manufacturing Company |
—
|
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: Colt's Manufacturing Company | Statement: [ArmaLite, soldDesignRightsTo, Colt's Manufacturing Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldDesignRightsTo Context triple: [ArmaLite, soldDesignRightsTo, Colt's Manufacturing Company]
-
A.
soldRightsTo
chosen
Indicates that one party has transferred ownership or usage rights of something to another party, typically in exchange for compensation.
-
B.
soldWorkTo
Indicates that one entity transferred ownership of a work (such as a product, artwork, or creation) to another entity in exchange for payment.
-
C.
soldWith
Indicates that one item is sold together with another item as part of the same transaction or offer.
-
D.
designedToSell
Indicates that something was intentionally created or configured for the purpose of being sold.
-
E.
soldBirthrightTo
Indicates that one entity transferred their birthright to another entity in exchange for something, relinquishing their original claim.
- 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_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:44 p.m.