Triple
T9710759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CZ 75 |
E235015
|
entity |
| Predicate | triggerGuard |
P48627
|
FINISHED |
| Object | rounded trigger guard (early models) |
—
|
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: rounded trigger guard (early models) | Statement: [CZ 75, triggerGuard, rounded trigger guard (early models)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerGuard Context triple: [CZ 75, triggerGuard, rounded trigger guard (early models)]
-
A.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
B.
guardType
chosen
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
C.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
D.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da8eaa08190b3ba148d85c5cec5 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.