Triple
T6396214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salvatore Carcano |
E143947
|
entity |
| Predicate | hasPartInventionType |
P41623
|
FINISHED |
| Object | bolt-action mechanism |
—
|
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: bolt-action mechanism | Statement: [Salvatore Carcano, hasPartInventionType, bolt-action mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInventionType Context triple: [Salvatore Carcano, hasPartInventionType, bolt-action mechanism]
-
A.
inventionType
Indicates the specific category or kind of invention that characterizes the relationship between an invention and its type.
-
B.
hasInventionProperty
Indicates that an entity possesses a specific characteristic, attribute, or quality related to an invention.
-
C.
hasKeyInvention
Indicates that an entity possesses or is associated with a primary or crucial invention.
-
D.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
E.
hasPartInHisDesign
chosen
Indicates that one entity is included as a component or element within the design or plan created by another entity.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068953968819083a94f5de3e11819 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.