Triple
T31989694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canik TP9 series |
E816829
|
entity |
| Predicate | importerInUnitedStates |
P173091
|
FINISHED |
| Object | Century Arms |
—
|
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: Century Arms | Statement: [Canik TP9 series, importerInUnitedStates, Century Arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importerInUnitedStates Context triple: [Canik TP9 series, importerInUnitedStates, Century Arms]
-
A.
USImporter
chosen
Indicates that an entity acts as an importer of goods or services into the United States in the context of a transaction or trade relationship.
-
B.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
C.
requiresFromUnitedStates
Indicates that one entity has a requirement that must be fulfilled specifically by the United States.
-
D.
imported
Indicates that something was brought into a country, system, or context from an external source.
-
E.
seeksFromUnitedStates
Indicates that an entity is seeking something (such as assistance, approval, resources, or action) from the United States.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 12:13 a.m.