Triple
T16546800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M38 carbine |
E401963
|
entity |
| Predicate | hasCartridgeType |
P91968
|
FINISHED |
| Object | rimmed rifle 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: rimmed rifle cartridge | Statement: [M38 carbine, hasCartridgeType, rimmed rifle cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCartridgeType Context triple: [M38 carbine, hasCartridgeType, rimmed rifle cartridge]
-
A.
requiresCartridgeSlotOf
Indicates that one entity needs to use or be connected to the cartridge slot provided by another entity in order to function or be compatible.
-
B.
hasCartridgesOrPods
Indicates that an entity possesses or is associated with cartridges or pods used for its operation or function.
-
C.
hasParentCartridge
Indicates that one cartridge is derived from, contained within, or otherwise hierarchically related as a child to another cartridge designated as its parent.
-
D.
cassetteTypeSupported
Indicates that a given system, device, or component is compatible with and can operate using a specified cassette type.
-
E.
intendedCartridgeStandard
chosen
Indicates that an item is designed to be used with, or conform to, a particular cartridge standard.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbe3fb48190bad143b50dc73c7e |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.