Triple
T35144071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I rifle |
E1014772
|
entity |
| Predicate | designFeaturesCombinedFrom |
P94092
|
FINISHED |
| Object | Italian Carcano design |
—
|
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: Italian Carcano design | Statement: [Type I rifle, designFeaturesCombinedFrom, Italian Carcano design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designFeaturesCombinedFrom Context triple: [Type I rifle, designFeaturesCombinedFrom, Italian Carcano design]
-
A.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
combinesFeaturesOf
chosen
Indicates that one entity integrates or merges characteristics, attributes, or functionalities originating from multiple other entities.
-
C.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
sharesDesignFeaturesWith
Indicates that two entities have similar or overlapping design characteristics, structures, or stylistic elements.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:02 p.m.