Triple
T16751949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krnka rifle |
E407102
|
entity |
| Predicate | loadingType |
P41759
|
FINISHED |
| Object | metallic cartridge |
—
|
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: metallic cartridge | Statement: [Krnka rifle, loadingType, metallic cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadingType Context triple: [Krnka rifle, loadingType, metallic cartridge]
-
A.
loadType
chosen
Indicates the manner or category of how something is loaded, such as the method, configuration, or type of loading applied in a given context.
-
B.
loadingMechanism
Indicates the method or system by which something is loaded into or onto another object or structure.
-
C.
loadBearingFor
Indicates that one entity structurally supports and carries the weight or load of another entity.
-
D.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
E.
refreshType
Indicates the manner or category of update applied to an entity, such as whether it is a full, partial, or incremental refresh.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa282bb08190992c9b61caa7a345 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.